copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2024-12-19 |
cloud-logs |
{{site.data.keyword.attribute-definition-list}}
{: #metadata}
{{site.data.keyword.logs_full_notm}} includes metadata fields that can be used to catalog and filter logs, grant user permissions and access to data, create log templates and template branches, and track anomalies. {: shortdesc}
{: #md-app-name}
The application name is the environment that produces and sends logs to {{site.data.keyword.logs_full_notm}}.
The following are samples of application names based on the log source:
Source | Application Name |
---|---|
Activity tracking events | ibm-audit-event |
Platform logs | ibm-platform-log |
{{site.data.keyword.openshiftlong_notm}} cluster | kubernetes.namespace_name |
{{site.data.keyword.containerlong_notm}} cluster | kubernetes.namespace_name |
Linux server | ${HOSTNAME} |
Windows server | ${COMPUTERNAME} |
{: caption="Application names" caption-side="bottom"} |
{: #md-sys-name}
The subsystem name is the service or application that produces and sends logs to {{site.data.keyword.logs_full_notm}}.
The following are samples of subsystem names based on the log source:
Source | Subsystem Name |
---|---|
Activity tracking events | CRNserviceName:instanceID |
VPC Activity tracking events | is:resourceType |
Platform logs | CRNserviceName:instanceID |
VPC Platform logs | is:resourceType |
{{site.data.keyword.openshiftlong_notm}} cluster | kubernetes.container_name |
{{site.data.keyword.containerlong_notm}} cluster | kubernetes.container_name |
Linux server | |
Windows server | ProviderName |
{: caption="Subsystem names" caption-side="bottom"} |