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 Investigator reactively dives deep into data to discover root cause in their own app or system. Their primary motivation is to fix the underlying issue.

​
Pain points

  • Requires deep knowledge of the system and an instinctual sense of observability data and data types.
  • Difficult to share learnings in a way that others can absorb and use going forward.
  • Digging through uncategorized or unrecognizable data, such as correlating instance IDs to services or interpreting obscurely named exporter data.

​
Common tasks

  • Explores observability data through advanced queries using the Metrics Explorer, Trace Explorer, and Logs Explorer.
  • Creates dashboards to pull together disparate observability data in a single place during an investigation, to save discoveries and measure the effectiveness of fixes.
  • Creates monitors to notify if fixes or improvements aren’t effective in the long run.

​
Connected personas

A Responder might become an Investigator if a remediation path isn’t discovered promptly, or if it requires something more difficult than a rollback.