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

traces_sampler example doesn't match the actual context provided

Abierto
  • ¿Algo no está bien?
#945 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@solnic ya está trabajando en esto.

Desde el 21/11/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Bug Elixir Traces Waiting for: Product Owner
Issue Description

The docs give an example on how to adjust the sample rate depending on the context. However, it appears the example doesn't match what ultimately gets reported in the Sentry dashboard.

Reproduction Steps

Add this config from the docs and you'll see that the op is never http.server for any http requests, but instead atoms like :GET and :POST

config :sentry,
  traces_sampler: fn sampling_context ->
    case sampling_context.transaction_context.op do
      IO.inspect(op, label: "Actual op") 
      "http.server" -> 0.1  # Sample 10% of HTTP requests
      _ -> 0.05             # Sample 5% of other operations
    end
  end
Expected Behavior

Sample code should work, or docs should be updated to match what the library actually does.

Actual Behavior

100% of the traces reported by my Phoenix app show up with an op of either db or http.server on the Sentry dashboard. But the op field in the context passed to traces_sampler is always something more detailed. For example, if I issue a GET request to /health-check, this is what the context actually looks like when I inspect it.

%{
  attributes: %{
    "url.path": "/health-check",
    "http.request.method": :GET,
    "client.address": "127.0.0.1",
    "network.peer.address": "127.0.0.1",
    "network.peer.port": 62201,
    "network.protocol.version": :"1.1",
    "url.scheme": :http,
    "user_agent.original": "curl/8.7.1",
    "server.address": "localhost",
    "server.port": 4001
  },
  name: :GET,
  op: :GET,
  trace_id: 68167592341524485616445320670865761234
}

However, in Sentry's dashboard, this shows up like this, with an op of http.server.

Image

So if I try to filter on http.server like the example shows, it doesn't work because op doesn't become http.server until some point after the traces_sampler function runs.

The same issue for db ops. In the context, they will show up as my_app.repo.query but report as db on the dashboard.

Elixir Version

1.18.4

SDK Version

11.0.4

Integration and Its Version

No response

Sentry Config

No response

Lenguaje dominante
Elixir
Estrellas
693
Forks
218
Merge medio
2 d 4 h
PR fusionados (30 d)
21

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 getsentry/sentry-elixir

Todos los issues de getsentry/sentry-elixir

Issues similares

Más issues de Elixir

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.