Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt

Use this file to discover all available pages before exploring further.

The Watcher proactively views their system behavior and performance, typically following a system event. Their primary motivation is to determine whether the system is working as intended. Most Chronosphere users in the developer personas can take on this role.

​
Pain points

  • Can’t recognize their system (or their part of it) in the data.
  • Don’t know what data is helpful or important to ascertain health of their system.
  • Want to track impact of recent changes, but can’t recognize or find the right data to do so.
  • Too many dashboards, too poorly organized to know where to look to view health or performance.

​
Common tasks

  • Finds a recent change event of interest to them, such as a deployment they started or a change to the telemetry configuration.
  • Observes real-time performance data for relevant parts of the system on a service page, anchored around an agnostic (non-negative) change event.
  • Compares current performance data to historical patterns using time range controls and the Metrics Explorer.

​
Connected personas

The Watcher becomes a Responder if poor performance is identified during their observation, and might be able to mitigate an issue before an alert triggers. After completing the mitigation action, they return to the Watcher role. If the change event involves launching a new service, the Watcher might need to act as a Librarian to find the correct data and organize it first.