Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

search_events always fails on self-hosted Sentry 25.7.0: /events/validate/ returns 404

Abierto
  • ¿Algo no está bien?
#1,355 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@chykB ya está trabajando en esto.

Desde el 6/10/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
64/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, backend

Línea de trabajo

Start at the search_events entry point and trace how GET /organizations/{org}/events/validate/ errors are handled before the events query. Reproduce the self-hosted Sentry 25.7.0 case, then verify that a 404 no longer prevents the events request and that successful search_events results are returned.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Since 0.37.0, search_events calls GET /api/0/organizations/{org}/events/validate/ before every events query (#1105, #1113). Our self-hosted Sentry 25.7.0 answers 404 on that endpoint. The tool treats the 404 as a fatal error, so search_events fails on every call, even though the events query itself would succeed.

Environment

  • @sentry/mcp-server 0.42.0, stdio
  • Self-hosted Sentry 25.7.0 (build 0ce69559)
  • Flags: --host=<self-hosted host> --organization-slug=<org> --project-slug=<project> --skills=inspect,triage
  • User auth token with event:read, project:read, org:read, alerts:read

Steps to reproduce

  1. Start the server with the flags above against a self-hosted Sentry 25.7.0.
  2. Call search_events with dataset: "errors", query: "level:error", statsPeriod: "24h".

Expected

The tool returns the matching error events.

Actual

API error (404): API request failed: Not Found

What we checked

With the same token, directly against the API:

Request Status
GET /organizations/{org}/events/validate/?project=<id>&dataset=errors&field=title 404
GET /organizations/{org}/events/?project=<id>&dataset=errors&field=title&field=count() 200
GET /organizations/{org}/events/?...&dataset=discover 200
GET /organizations/{org}/events/?...&dataset=spans 200
GET /organizations/{org}/events/?...&dataset=ourlogs 200

search_issues and get_sentry_resource work on 0.42.0. On 0.36.0, the last version without the validate call, search_events returns results against the same instance with the same flags. We pinned 0.36.0 as a workaround.

Suggestion

When /events/validate/ answers 404, skip validation and run the events query, maybe with a warning in the tool output. A 404 there most likely means that the server does not have the endpoint, and not that the query is invalid.

If the maintainers prefer not to fall back: which Sentry version is the minimum for search_events? A version check or a note in the self-hosted docs would help.

Related

  • #1253 handles a generic 400 from validateEvents. This report is about a 404.
  • #937 reports a 404 from search_events on the hosted server. That may be a different cause.
Lenguaje dominante
TypeScript
Estrellas
938
Forks
166
Merge medio
1 d 7 h
PR fusionados (30 d)
156

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de getsentry/toolkit

Todos los issues de getsentry/toolkit

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.