Skip to main content

Chronosphere

Dig through Chronosphere metrics, logs, and traces when an alert fires.

Tools

31 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

31 tools found.

  • Get dashboard

    Tool name: get_dashboard

    Get dashboards resource

  • Get drop rule

    Tool name: get_drop_rule

    Get drop-rules resource

  • Get events metadata

    Tool name: get_events_metadata

    List properties you can query on events

  • Get log

    Tool name: get_log

    Get a full log message by its ID.

  • Get log histogram

    Tool name: get_log_histogram

    Get histogram of logs from a given query

  • Get mapping rule

    Tool name: get_mapping_rule

    Get mapping-rules resource

  • Get monitor

    Tool name: get_monitor

    Get monitors resource

  • Get notification policy

    Tool name: get_notification_policy

    Get notification-policies resource

  • Get recording rule

    Tool name: get_recording_rule

    Get recording-rules resource

  • Get rollup rule

    Tool name: get_rollup_rule

    Get rollup-rules resource

  • Get slo

    Tool name: get_slo

    Get slos resource

  • List dashboards

    Tool name: list_dashboards

    List dashboards resources

  • List drop rules

    Tool name: list_drop_rules

    List drop-rules resources

  • List events

    Tool name: list_events

    List events from a given query

  • List events label values

    Tool name: list_events_label_values

    List values for a given label name

  • List log field names

    Tool name: list_log_field_names

    List field names of logs

  • List log field values

    Tool name: list_log_field_values

    List field values of logs

  • List mapping rules

    Tool name: list_mapping_rules

    List mapping-rules resources

  • List monitors

    Tool name: list_monitors

    List monitors resources

  • List notification policies

    Tool name: list_notification_policies

    List notification-policies resources

  • List prometheus label names

    Tool name: list_prometheus_label_names

    Returns the list of label names (keys) available on metrics that match the given selectors.

  • List prometheus label values

    Tool name: list_prometheus_label_values

    Returns the list of values for a specific label name, optionally filtered by selectors.

  • List prometheus series

    Tool name: list_prometheus_series

    Returns the complete time series (full label sets with all key-value pairs) that match the given selectors.

  • List recording rules

    Tool name: list_recording_rules

    List recording-rules resources

  • List rollup rules

    Tool name: list_rollup_rules

    List rollup-rules resources

  • List slos

    Tool name: list_slos

    List slos resources

  • List traces

    Tool name: list_traces

    List traces from a given query

  • Query logs range

    Tool name: query_logs_range

    Execute a range query for logs.

  • Query prometheus instant

    Tool name: query_prometheus_instant

    Evaluates a Prometheus instant query at a single point in time

  • Query prometheus range

    Tool name: query_prometheus_range

    Executes a Prometheus PromQL query over a specified time range and returns time series data points as JSON.

  • Render prometheus range query

    Tool name: render_prometheus_range_query

    Evaluates a Prometheus expression query over a range of time and renders it as a PNG image.

Compatibility

Connect Chronosphere to the clients your teams already use

27 AI clients can connect to Chronosphere through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Chronosphere through Runlayer?

One approved path

Approve Chronosphere once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions