Grafana Cloud Enterprise Open source

Azure Monitor annotations

Annotations overlay rich event information on top of graphs. You can use Azure Monitor Log Analytics queries to create annotations that mark important events, deployments, alerts, or other significant occurrences on your dashboards.

Before you begin

  • Ensure you have configured the Azure Monitor data source.
  • You need access to a Log Analytics workspace containing the data you want to use for annotations.
  • Annotations use Log Analytics (KQL) queries only. Metrics, Traces, and Azure Resource Graph queries are not supported for annotations.

Create an annotation query

To add an Azure Monitor annotation to a dashboard:

  1. Open the dashboard where you want to add annotations.
  2. Click Dashboard settings (gear icon) in the top navigation.
  3. Select Annotations in the left menu.
  4. Click Add annotation query.
  5. Enter a Name for the annotation (e.g., “Azure Activity”, “Deployments”).
  6. Select your Azure Monitor data source.
  7. Choose the Logs service.
  8. Select a Resource (Log Analytics workspace or Application Insights resource).
  9. Write a KQL query that returns the annotation data.
  10. Click Apply to save.

Query requirements

Your KQL query should return columns that Grafana can use to create annotations:

ColumnRequiredDescription
TimeGeneratedYesThe timestamp for the annotation. Grafana uses this to position the annotation on the time axis.
TextRecommendedThe annotation text displayed when you hover over or click the annotation.
Additional columnsOptionalAny other columns returned become annotation tags.

Note

Always include a time filter in your query to limit results to the dashboard’s time range. Use the $__timeFilter() macro.

Annotation query examples

The following examples demonstrate common annotation use cases.

Azure Activity Log events

Display Azure Activity Log events such as resource modifications, deployments, and administrative actions:

kusto
AzureActivity
| where $__timeFilter(TimeGenerated)
| where Level == "Error" or Level == "Warning" or CategoryValue == "Administrative"
| project TimeGenerated, Text=OperationNameValue, Level, ResourceGroup, Caller
| order by TimeGenerated desc
| take 100

Deployment events

Show deployment-related activity:

kusto
AzureActivity
| where $__timeFilter(TimeGenerated)
| where OperationNameValue contains "deployments"
| project TimeGenerated, Text=strcat("Deployment: ", OperationNameValue), Status=ActivityStatusValue, ResourceGroup
| order by TimeGenerated desc

Application Insights exceptions

Mark application exceptions as annotations:

kusto
AppExceptions
| where $__timeFilter(TimeGenerated)
| project TimeGenerated, Text=strcat(ProblemId, ": ", OuterMessage), SeverityLevel, AppRoleName
| order by TimeGenerated desc
| take 50

Custom events from Application Insights

Display custom events logged by your application:

kusto
AppEvents
| where $__timeFilter(TimeGenerated)
| where Name == "DeploymentStarted" or Name == "DeploymentCompleted"
| project TimeGenerated, Text=Name, AppRoleName
| order by TimeGenerated desc

Security alerts

Show security-related alerts:

kusto
SecurityAlert
| where $__timeFilter(TimeGenerated)
| project TimeGenerated, Text=AlertName, Severity=AlertSeverity, Description
| order by TimeGenerated desc
| take 50

Resource health events

Display resource health status changes:

kusto
AzureActivity
| where $__timeFilter(TimeGenerated)
| where CategoryValue == "ResourceHealth"
| project TimeGenerated, Text=OperationNameValue, Status=ActivityStatusValue, ResourceId
| order by TimeGenerated desc

VM start and stop events

Mark virtual machine state changes:

kusto
AzureActivity
| where $__timeFilter(TimeGenerated)
| where OperationNameValue has_any ("start", "deallocate", "restart")
| where ResourceProviderValue == "MICROSOFT.COMPUTE"
| project TimeGenerated, Text=OperationNameValue, VM=Resource, Status=ActivityStatusValue
| order by TimeGenerated desc

Autoscale events

Show autoscale operations:

kusto
AzureActivity
| where $__timeFilter(TimeGenerated)
| where OperationNameValue contains "autoscale"
| project TimeGenerated, Text=strcat("Autoscale: ", OperationNameValue), Status=ActivityStatusValue, ResourceGroup
| order by TimeGenerated desc

Customize annotation appearance

After creating an annotation query, you can customize its appearance:

SettingDescription
ColorChoose a color for the annotation markers. Use different colors to distinguish between annotation types.
Show inSelect which panels display the annotations.
Filter byAdd filters to limit when annotations appear.

Best practices

Follow these recommendations when creating annotations:

  1. Limit results: Always use take or limit to restrict the number of annotations. Too many annotations can clutter your dashboard and impact performance.

  2. Use time filters: Include $__timeFilter() to ensure queries only return data within the dashboard’s time range.

  3. Create meaningful text: Use strcat() or project to create descriptive annotation text that provides context at a glance.

  4. Add relevant tags: Include columns like ResourceGroup, Severity, or Status that become clickable tags for filtering.

  5. Use descriptive names: Name your annotations clearly (e.g., “Production Deployments”, “Critical Alerts”) so dashboard users understand what they represent.

Troubleshoot annotations

If annotations aren’t appearing as expected, try the following solutions.

Annotations don’t appear

  • Verify the query returns data in the selected time range.
  • Check that the query includes a TimeGenerated column.
  • Test the query in the Azure Portal Log Analytics query editor.
  • Ensure the annotation is enabled (toggle is on).

Too many annotations

  • Add more specific filters to your query.
  • Use take to limit results.
  • Narrow the time range.

Annotations appear at wrong times

  • Verify the TimeGenerated column contains the correct timestamp.
  • Check your dashboard’s timezone settings.