Application & Subsystem Names - MLKEREN/SOFTWARE-DOC-DEV-MIYA-KEREN GitHub Wiki

UNDER CONSTRUCTION

In order for us to help you make sense of your logs, metrics and traces, and analyze it most effectively, we require that you organize your data using two metadata fields: Application and Subsystem name.

These filters will ultimately give value to your data in a manner that is most meaningful for you.

The filters section occupies the left side of the Logs tab. It enables the selection of specific values to be queries per filter. By default, the screen opens with application, subsystem, and severity filters, but the filters are completely customizable and metadata or log field are available.

Application name: Environment that sends logs. May be production, development and staging environment.

Subsystem: Service or application that sends logs.

https://coralogix.com/blog/analyzing-log-data-important/

Looking Two metadata that accompany logs themselves and are generated in the cloud sending the clouds. Choose what I want from this data in order to filter the dashboard according to my needs.

To identify from where the logs

Custom Application name

In Coralogix Application Name typically represents the environment name. You can map the Application Name differently if you have many Kubernetes clusters or some custom setup. The following example shows mapping application name to production-$NAMESPACE for Telegraf Operator deployed in the production Kubernetes cluster.

    infra: |
      [outputs.opentelemetry](/MLKEREN/SOFTWARE-DOC-DEV-MIYA-KEREN/wiki/outputs.opentelemetry)
        [outputs.opentelemetry.coralogix]
          private_key = "<private-key>"
          application = "production-$NAMESPACE"
          subsystem = "$HOSTNAME"=