/actuator/prometheus on the ConfigSync service. All custom metrics use the configsync_ prefix for easy discovery and to avoid collisions with other applications.
The following metrics are exposed by the ConfigSync service:
configsync_resource_update_errors_total(counter) - The total number of errors encountered while updating resources.configsync_out_of_sync(gauge) - The number of resources that are out of sync. Only insubmode.configsync_sync_seconds(summary) - The time taken to sync resources.configsync_sync_seconds_max(gauge) - The maximum time taken to sync resources.
Annotations
Annotations are visual markers that appear on Grafana time-series graphs to highlight when specific events occurred. They provide context by overlaying event information directly onto your graphs, making it easier to correlate Fusion system behavior with ConfigSync activities. When monitoring ConfigSync in Grafana graphs, annotations help you:- Identify the cause of metric changes - Correlate spikes or dips in metrics with specific ConfigSync events like Git commits or Fusion configuration updates
- Track deployment timelines - Visualize when configuration changes were applied to your Fusion cluster
- Debug synchronization issues - Pinpoint when files changed in Git versus when they were applied to Fusion
configsync_git_file_changes_total(counter) - The number of files changes in Git from Fusion.configsync_fusion_updates_total(counter) - The number of operations applied to Fusion from Git.configsync_git_commits_total(counter) - The number of commits by type. You can use labels to filter by the type of commit.updates-from-fusion- Updates created by ConfigSyncexplicit- Updates created by users and applied to Fusion
Example Grafana annotation queries
The following example queries can be used as annotation sources in Grafana.Annotate when Git files changed
increase(configsync_git_file_changes_total[1m]) > 0
Annotate when Fusion was updated
increase(configsync_fusion_updates_total[1m]) > 0
Annotate explicit user commits
increase(configsync_git_commits_total{commit_type="explicit"}[1m]) > 0