# Search logs for a reported error or event

> Search logs for a reported error or event: 2 companies fully do it, 6 with a limit, 11 carry the tag. Every listing in Observability & incidents with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/observability.search-logs/
- Markdown: https://www.anchorterminal.com/niches/observability.search-logs/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/observability.search-logs/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/observability.search-logs/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 6 | 11 | 16 | 8 |

## What counts as done

Matching log lines with timestamps and the query used, a count of total matches and a marker when results were truncated, from at most three queries.

How agents ask for it: search the logs for this request id; find errors for this user in the last hour; is this event in the logs; what did the server log when it failed

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Datadog MCP Server (Datadog, Inc.)**: search_datadog_logs takes a query and time range, analyze_datadog_logs counts matches in SQL, and responses are truncated with instructions for fetching more.
- **Grafana MCP Server (Raintank Inc., d/b/a Grafana Labs)**: query_loki_logs takes LogQL, caps lines at --max-loki-log-limit (100) and requests one extra line to detect truncation, and Loki metric queries count matches. PII redaction is still an open request (#1124).

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Axiom MCP Server (Axiom, Inc.)**: APL search and count in one queryDataset call, but the docs state no result size cap and no truncation marker, and tool schemas are only visible after sign-in.
- **Better Stack (Better Stack, Inc.)**: One SQL query returns matching lines and counts, and Plan query windows estimates rows read, but no result size limit or truncation marker is documented.
- **Honeycomb MCP (Hound Technology, Inc. d/b/a Honeycomb)**: run_query is an aggregation query that returns counts and breakdowns; the docs show no raw-row result with a truncation marker, so matching lines come through traces and span details instead.
- **New Relic MCP Server (New Relic, Inc.)**: list_recent_logs, get_log_statistics and NRQL over Log give lines and counts, but no result cap or truncation marker is documented and tool schemas need a signed-in session.
- **Rootly MCP Server (Rootly Inc.)**: The observability toolset covers Rootly Observability logs and patterns, but the docs give no query syntax, match count or truncation marker for it.
- **Sentry MCP (Functional Software, Inc. d/b/a Sentry)**: search_logs returns lines, counts and time series and accepts Sentry search syntax, but an embedded model translates every query, and no truncation marker is documented.

- not this job: Causely MCP server (Causely, Inc.): get_logs returns live or diagnosis-time logs for one entity; there is no search syntax, match count or truncation marker.
- not this job: Cronitor MCP server (Cronitor): The docs call the server a control plane, not a data plane; there is no log search.
- not this job: incident.io API (Pineapple Technology Ltd.): No log query tool; ask_telemetry returns a synthesised answer with no documented match count or truncation marker.
- not this job: PagerDuty MCP Server (PagerDuty, Inc.): No log search; browse_activity returns PagerDuty's own log entries only.

## What stops agents finishing

- empty result returned where the query failed
- no cap on range or bytes, so one query floods the context
- personal data in logs that policy bars from the model provider

## Around it

Before: support.ticket-received, observability.investigate-alert. After: observability.error-to-fix, code.open-pr.

## Where this comes from

Weight 16 of 100 in Observability & incidents: 8 of 42 accounts (Better Stack, Axiom, CloudWatch, Loki through Grafana)

As data: https://www.anchorterminal.com/api/v1/use-cases/observability.search-logs.json, or the MCP tool get_use_case with id observability.search-logs. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
