Chronosphere API

Name: Chronosphere API API
Brand: Chronosphere API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey4 EndpointsREST

For Agents

Manage Chronosphere observability configuration — list and create collections, list monitors, and execute PromQL metric queries.

Quickstart

Get started with Chronosphere API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"query a metric in Chronosphere"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chronosphere API API.

List existing telemetry collections via /api/v1/config/collections

Create a new collection that groups related metrics through POST /api/v1/config/collections

List all configured alert monitors via /api/v1/config/monitors

Execute PromQL metric queries against the time-series store via /data/metrics/api/v1/query

GET STARTED

Start building with Chronosphere API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Chronosphere API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Chronosphere API, keeping it validated and agent-ready. Chronosphere is a cloud-native observability platform built on M3 and OpenTelemetry that ingests metrics, logs, and traces at scale. The API enables programmatic management of observability configurations — collections that group related telemetry, monitors that fire alerts on metric thresholds, and PromQL-style metric queries against the time-series store. It is used by platform and SRE teams who manage observability as code rather than through the UI.

Use Cases

Patterns agents use Chronosphere API API for, with concrete tasks.

★ Observability as Code

Platform teams manage Chronosphere collections and monitors through Terraform or in-house tooling rather than clicking through the UI. The /api/v1/config/collections endpoint supports both list and create, allowing automated provisioning of telemetry groupings as new services come online. This keeps observability configuration in version control alongside the applications it monitors.

POST a new collection to /api/v1/config/collections named 'checkout-service' with the appropriate labels and verify it appears in a follow-up GET

Scheduled Metric Queries for Reports

SRE teams run scheduled PromQL queries to populate weekly reliability reports — error rates, latency percentiles, saturation metrics. The /data/metrics/api/v1/query endpoint accepts a PromQL expression and returns the time-series result, which a reporting job then formats into stakeholder-friendly summaries without anyone needing to log into Chronosphere.

Execute the PromQL query 'rate(http_requests_total{job="checkout"}[5m])' against /data/metrics/api/v1/query and return the result

Monitor Inventory Audit

Large organisations accumulate hundreds of alert monitors that drift over time — duplicates, monitors on deprecated services, monitors with stale thresholds. The /api/v1/config/monitors endpoint lists every configured monitor so an audit job can flag duplicates, monitors without owners, or monitors that have not fired in months for cleanup.

List all monitors via /api/v1/config/monitors and produce a report of monitors lacking an owner label

Agent-Driven Incident Triage

An AI agent helping an on-call engineer triage an incident calls Chronosphere through Jentic to query the current value of relevant metrics and check which monitors are firing. The agent searches Jentic for 'query a metric in Chronosphere', loads the query operation, and runs the relevant PromQL expressions to surface a focused incident summary.

Search Jentic for 'query a metric in Chronosphere', load /data/metrics/api/v1/query, and run three PromQL expressions for current latency, error rate, and saturation

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for chronosphere api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/config/collections

List all collections

POST

/api/v1/config/collections

Create a new collection

GET

/api/v1/config/monitors

List all monitors

GET

/data/metrics/api/v1/query

Execute a PromQL metric query

GET

/api/v1/config/collections

List all collections

POST

/api/v1/config/collections

Create a new collection

GET

/api/v1/config/monitors

List all monitors

GET

/data/metrics/api/v1/query

Execute a PromQL metric query

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Chronosphere apiToken and tenant identifier are stored encrypted in the Jentic vault. Agents receive scoped access — neither the raw token nor tenant-specific URLs leak into the agent context.

Intent-based discovery

Agents search by intent (e.g., 'query a metric in Chronosphere') and Jentic returns the matching operation along with its parameter schema and tenant binding.

Time to first call

Direct integration: 1-2 days for auth, tenant resolution, and PromQL handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

New Relic

Full-stack observability platform with metrics, logs, traces, and APM

Choose New Relic when you want bundled APM and frontend monitoring rather than the metrics-first M3 architecture Chronosphere uses

Complementary

PagerDuty

Incident response and on-call paging, often paired with observability platforms

Pair with Chronosphere to escalate firing monitors to on-call engineers via paging policies

Complementary

Sentry

Application error monitoring with stack traces and release tracking

Pair with Chronosphere when correlating infrastructure metrics with application-level errors and exception rates

FAQs

Specific to using Chronosphere API API through Jentic.

Why is there no official OpenAPI spec for Chronosphere API?

Chronosphere does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Chronosphere API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Chronosphere API use?

Chronosphere uses an API token passed in the apiToken header. The base URL is tenant-specific (https://{tenant}.chronosphere.io) so both the token and the tenant name need to be configured. Through Jentic, the token is stored encrypted in the vault and the agent receives a scoped reference.

Can I run PromQL queries through the Chronosphere API?

Yes. The /data/metrics/api/v1/query endpoint accepts a PromQL expression and returns the matching time-series result, which is the standard pattern for querying metrics programmatically without using the Chronosphere UI.

Can I create collections programmatically?

Yes. The POST /api/v1/config/collections endpoint creates a new collection with the supplied labels and configuration, which lets platform teams provision observability groupings as part of service onboarding scripts or Terraform pipelines.

What are the rate limits for the Chronosphere API?

Specific rate limits are not declared in the OpenAPI spec — Chronosphere applies tenant-level throttling. Plan to backoff on 429 responses and avoid tight polling against /data/metrics/api/v1/query for high-cardinality expressions.

How do I run a PromQL query through Jentic?

Run pip install jentic, search for 'query a metric in Chronosphere', load the /data/metrics/api/v1/query operation, and execute with the PromQL expression as the query parameter. Jentic injects the apiToken header and the tenant from the vault.