[telemetry] policyengine-simulation-entry: HTTP 500 without recorded exception on `/jobs/{job_id}` (136c8e506b323978)

Abierto
  • ¿Algo no está bien?
#4,216 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, observability

Línea de trabajo

Start by inspecting the /jobs/{job_id} route and its request logs for the reported time window; the matching records require access to the policyengine-observability project. Compare the production and staging failures and the related fingerprints to find where the HTTP 500 is produced without a recorded exception. The issue is resolved when the cause is identified and the route no longer returns unexplained 500 responses.

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

Descripción

service: policyengine-simulation-entry telemetry-error

The daily telemetry error report opened this issue for a production error group. Each run replaces the marked section below with the latest day's measures; text outside it is kept.

Error group 136c8e506b323978
  • Kind: failed_request (fingerprint algorithm 2)
  • Service: policyengine-simulation-entry
  • Response: HTTP 500
  • Most frequent route: /jobs/{job_id}
  • Window: 2026-11-06 00:00 EST to 2026-11-07 00:00 EST (24 hours)
Measure Production Staging
Occurrences 2 0
Affected requests 2 0
Observability IDs 2 0
Error rate on affected routes 0.15% (2 of 1,355 requests) n/a
Occurrences per hour 0.08 0.00
Occurrences per hour, previous 7 days 0.39 0.01
First seen in the last 8 days 2026-10-30 14:33 EDT 2026-11-05 09:14 EST
Last seen 2026-11-06 16:59 EST 2026-11-05 09:14 EST

Related fingerprints (sharing traces): 2ccd25f73380b2e8, 98f16312752738db, 67304635d27f9ace

Matching log records in Logs Explorer, for the window only. It needs read access to the policyengine-observability project.

Lenguaje dominante
Python
Estrellas
18
Forks
33
Merge medio
2 d 17 h
PR fusionados (30 d)
108

Preparar el entorno

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 PolicyEngine/policyengine-api

Todos los issues de PolicyEngine/policyengine-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.