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.
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:
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.
System
On the System tab, the Target info metric name used to query target info can be configured.
Was this page helpful?
Related resources from Grafana Labs


