Chronicle Metrics

This page lists and explains the available Chronicle metrics.

Each metric is listed with its description, schema, why it matters, and recommended actions. It also includes technical details, including metric type and aggregation strategy.

These metrics are stored in separate folders based on the name of the metric. These folders are located within the configured storage location (/var/lib/posit-chronicle/data by default).

chronicle_status

This metric tracks the basic status of the Chronicle server. It helps administrators ensure that the Chronicle server is correctly configured and operational.

Schema

Attribute Type Description
timestamp date-time The time that this status represents.
server_start_time date-time The timestamp when the Chronicle Server started.
server_version string The version of the Chronicle Server.
agent_count int The number of Chronicle Agents that have sent data to the Chronicle Server.
agent_timestamp date-time The timestamp of the most recent data received from a Chronicle Agent.
promoted_metrics_count int The number of unique metric names that have been refined.
promoted_metrics_timestamp date-time The timestamp of the most recent data refinement.
storage_timestamp date-time The timestamp of the most recent successful data storage.
failed_storage_timestamp date-time The timestamp of the most recent data storage error.

Why this metric matters

  • System health monitoring: Quickly identify when Chronicle Server is operational and functioning correctly
  • Data integrity verification: Confirm that metrics are being refined and stored successfully
  • Agent connectivity: Verify that Chronicle Agents are properly communicating with the server
  • Storage reliability: Monitor for any potential storage failures or issues
  • Resource planning: Track server uptime and ensure proper maintenance scheduling

up

This metric tracks the operational status of Chronicle agents. It helps administrators ensure that the Chronicle agents are correctly configured and operational. Indicates whether the Chronicle agent was able to scrape Prometheus metrics from Workbench and Connect.

Schema

Attribute Type Description
up boolean True (1) when the agent is running. Use the timestamp to understand the status.
service string The name of the product that produced the metric - either workbench or connect.

Why this metric matters

  • Operational visibility: Provides insight into Chronicle Agent status across your environment
  • Troubleshooting efficiency: Identify which agents require attention
  • Deployment validation: Confirm that newly deployed agents are properly registered and functioning
  • Infrastructure reliability: Monitor agent health to ensure continuous data collection and reporting
  • Change management: Track the impact of system changes on agent operational status
Back to top