Observability: 11 read-only integrations
Each page lists the exact tools Triagic exposes and the mechanism that keeps them read-only. Setup steps for every one live on the observability docs page. 14-day trial, no card.
- SentryPull issues, events, and stack traces. Works with Sentry-compatible backends (GlitchTip).annotation-vetted tools
- PrometheusQuery metrics and alerting rules.annotation-vetted tools
- OpenSearchSearch application logs and indices.8 tools
- ElasticsearchSearch application logs and documents, inspect mappings and shards. The bundled tools are read-only.4 tools
- DatadogRead monitors, logs, metrics, and incidents. Write tools stay disabled.23 tools
- GrafanaSearch dashboards, datasources, incidents, and alert rules. Write tools stay disabled. Runs the official image via Docker.annotation-vetted tools
- PagerDutyRead incidents, on-call schedules, and escalation policies. Write tools stay disabled.annotation-vetted tools
- SplunkRun SPL searches and read index and knowledge-object metadata. Needs the MCP Server app (Splunkbase 7931) installed on the instance.14 tools
- New RelicRun NRQL queries and read entities, alerts, and open incidents. Writes are not blocked. Use a key from a read-only user.13 tools
- DynatraceRun DQL against Grail and read problems, vulnerabilities, exceptions, Kubernetes events and Davis analyzers. Needs a Dynatrace platform environment (…apps.dynatrace.com). DQL is billed by data scanned, so each server gets a Grail budget.13 tools
- HoneycombRun Honeycomb queries and BubbleUp, look up traces and spans, and read boards, triggers and SLOs. Connects to Honeycomb's hosted server with a Management API key.24 tools
Connect one and ask it something
Install the desktop app, add a read-only credential for one system, and run a real investigation against it.