Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
SRE and observability agent - Agent - OpenSmartRoute
Agentv1.0.0
SRE and observability agent
Reads logs, traces, metrics and alerts to find the root cause of an incident, ranks the errors by impact, correlates them with deploys and proposes the fix and the runbook step; writes the postmortem
Part of the example catalogue (examples/targets.yaml).
Reads logs, traces, metrics and alerts to find the root cause of an incident, ranks the errors by impact, correlates them with deploys and proposes the fix and the runbook step; writes the postmortem timeline.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - nothing else to configurecurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'# or pin it on the OpenAI-compatible endpoint: {"model": "sre-agent", ...}
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
Installed into a catalogue, chosen by a router
Install SRE and observability agent and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
When a provider is down or over quota the request moves on; the trace says it did.
sre-agent.ocm.jsonjson
{
"ocm": "1",
"id": "sre-agent",
"kind": "agent",
"name": "SRE and observability agent",
"description": "Reads logs, traces, metrics and alerts to find the root cause of an incident, ranks the errors by impact, correlates them with deploys and proposes the fix and the runbook step; writes the postmortem timeline.",
"capabilities": {
"domains": [
"observability",
"coding"
],
"actions": [
"reasoning",
"extract",
"planning",
"action",
"summarize",
"generation"
],
"languages": [
"en"
],
"modalities": [
"text"
],
"max_complexity": 1,
"min_complexity": 0.4,
"supports_tools": true,
"supports_streaming": true,
"tags": [
"autonomous",
"observability"
]
},
"constraints": {
"data_boundary": "public",
"pii_allowed": true
},
"cost": {
"usd_per_1k_tokens": 0.008
},
"latency_ms": 9000,
"quality_prior": 0.84,
"examples": [
"Find the root cause of the checkout latency alert from these traces and logs.",
"Why did the error rate of the payments service spike after the 14:00 deploy?",
"Summarise the errors in this log excerpt and rank them by impact.",
"Write the postmortem timeline for last night's outage from these alerts."
],
"publisher": "OpenSmartRoute",
"version": "1.0.0"
}
Fetch it by URL: GET /api/v1/registry/sre-agent/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.