Menu
Grafana Cloud

Configure Application Observability

Editor and Admin users can configure the Application Observability plugin.

Data source

Configure default data source for each signal type. Changes are saved on selection.

On the Data source tab, the default data source for each signal type can be configured including: metrics, logs, and traces.

By default, the default provisioned data sources for the stack will be used. This enables easier onboarding, allowing only traces to be sent, and necessary metrics to be generated from traces.

If you are using a custom data source, metrics generation is not needed and can be disabled to reduce usage and billing.

Logs query

On the Logs query tab, the default log queries and formatting can be configured.

Logs query, without namespace

Configure the logs query to execute in the logs tab if service.namespace resource attribute is not provided. Available variables: $job, and $serviceName.

Logs query, with namespace

Configure the logs query to execute in the logs tab if service.namespace resource attribute is provided. Available variables: $job, $serviceName, and $serviceNamespace.

Logs query formatting

Specify the formatting section of a log query that is automatically appended to the end of logs queries to improve readability.

For example, the default formatting appended to log queries is:

LogQL
line_format "\u001b[1m{{if .severity}}{{alignRight 5 .severity}}{{end}}\u001b[0m \u001b[90m[{{alignRight 10 .resources_service_instance_id}}{{if .attributes_thread_name}}/{{alignRight 20 .attributes_thread_name}}{{end}}]\u001b[0m \u001b[36m{{if .instrumentation_scope_name }}{{alignRight 40 .instrumentation_scope_name}}{{end}}\u001b[0m{{if .traceid}} \u001b[37m\u001b[3m[traceid={{.traceid}}]{{end}}: {{.body}}"

Important: the formatting is automatically applied at the end of the actual query. Messing this up can lead to invalid queries.

Semantics

Use the semantics configuration tab to configure which attributes are used for grouping and filtering data in Application Observability.

Deployment environment attribute and value

By default Application Observability uses the OpenTelemetry recommended attribute deployment.environment to distinguish environments. A custom attribute can be selected from a list of possible attributes from the data.

Note

It is recommended to use an attribute that is available on all trace data ingested into Grafana Cloud.

Application Observability will select a default value that resembles the production environment. A custom value can be set in the Default environment section.

Group and filter attributes

To enable data to be grouped and filtered in Application Observability, first add the necessary attributes to traces and then select them from a list of available attributes in Application Observability.

By default you can group and filter by the deployment environment.

Warning

Adding additional group and filter attributes contributes to your data usage and billing.

Think carefully about the cardinality of your data and select attributes with minimal variation in value, for example geographical region and cloud provider will have less cardinality than instance id.

System

Use the system configuration tab to configure system-wide settings.

Target info metric name

On the System tab, the Target info metric name used to query target info can be configured.

Metrics generation

Enable or disable metrics generation for the default provisioned Traces data source for the stack.

Note

Metrics generation can safely be disabled if you are using a custom data source.