-
Task
-
Resolution: Won't Do
-
Normal
-
None
-
Logging 5.5.0
-
False
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
NEW
-
-
Logging (Core) - Sprint 219, Logging (Core) - Sprint 220, Log Collection - Sprint 221
- Add a new "TenantID" field to the Loki output struct, to allow the user to specify a fixed tenant value.
- Update both Fluentd and Vector forwarder implementations to conform to this API doc, in particular:
- Default behaviour is equivalent to 'TenantKey: log_type'
- Special TenantID value '-' means use single-tenant mode, no tenant ID.
type Loki struct { // TenantKey identifies a log record field to use as the Loki tenant-ID. // // Default: 'log_type' (one of [application, infrastructure, audit]) // // +optional TenantKey string `json:"tenantKey,omitempty"` // TenantID is a fixed string value to use as the Loki tenant-ID. // // The special value '-' means use single-tenant mode, no tenant ID. // // +optional TenantID string `json:"tenantID,omitempty"`
- clones
-
LOG-2299 Loki tenant configuration invalid for fluentd output plugin used
- Closed
- links to