-
Epic
-
Resolution: Done
-
Critical
-
Logging 5.4.1
-
Cluster-ID
-
5
-
False
-
None
-
False
-
Not Selected
-
NEW
-
To Do
-
Impediment
-
VERIFIED
-
0% To Do, 0% In Progress, 100% Done
Goal
Add the openshift cluster ID to log records.
The cluster ID is part of the `clusterversion` resource, can be retrieved with:
oc get clusterversion/version -o jsonpath='{.spec.clusterID}{"\n"}'
Why is this important?
When logs from multiple clusters are aggregated in the same store, it must be possible to distinguish logs from different clusters.
Scenarios
- ACM (Advanced Cluster Manager) may aggregate logs from multiple managed clusters.
- RHOBS (Red Hat Observability Service) manages multiple clusters on behalf of multiple customers.
- HyperShift may aggregate logs from many sub-clusters.
- Telco customers may want to aggregate logs from many edge clusters in a single NOC (Network Operation Centre)
There are likely to be other scenarios.
Acceptance Criteria
- All log records, of all types (application, infrastructure, audit), MUST have a new field `openshift.cluster_id` set to the value of the cluster ID.
- CI tests, technical enablement slides etc.
Notes
- Must be added to vector and fluentd
- blocks
-
LOG-2135 [spike] Investigate use of logging in multi-cluster ACM setting.
- Closed
-
OBSDA-155 Extend the log record envelope to identify the source OCP cluster of a log record.
- Closed
- is documented by
-
RHDEVDOCS-4420 Add a unique cluster name or identifier to the log record
- Closed
- relates to
-
LOG-2904 [spike] Investigate vector changes required to enable forwarding to syslog
- Closed
- links to
- mentioned on