You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I notice that we have an ongoing work on the phoenix_backend. However, I have not much context on what's the original plan and what's the end goal like.
I have setup a super basic Phoenix + Ecto application integrated with opentelemetry_phoenix and opentelemetry_ectohere. It's based on what we have on basic_elixir, so we have docker compose setup and user can run and play around with it locally with ease.
I'm thinking down the road, we could extend the example to configure otel-collector-config.yaml to export the traces directly to service like honeycomb and Lightstep as well.
Do you think it would be good to include that into this repository as well? If yes, should we replace the existing phoenix_backend example, or create a new folder?
The text was updated successfully, but these errors were encountered:
Yes, that would be great, including the idea to have it include optional configuration for exporting to services like honeycomb and lightstep.
Phoenix and beam-telemetry in general seem to be where many people will start coming to Otel from with the intention of getting spans and right now I think the docs and examples don't meet them where they are but instead starts from a blank beginning.
Hi, I notice that we have an ongoing work on the
phoenix_backend
. However, I have not much context on what's the original plan and what's the end goal like.I have setup a super basic Phoenix + Ecto application integrated with
opentelemetry_phoenix
andopentelemetry_ecto
here. It's based on what we have onbasic_elixir
, so we have docker compose setup and user can run and play around with it locally with ease.I'm thinking down the road, we could extend the example to configure
otel-collector-config.yaml
to export the traces directly to service like honeycomb and Lightstep as well.Do you think it would be good to include that into this repository as well? If yes, should we replace the existing
phoenix_backend
example, or create a new folder?The text was updated successfully, but these errors were encountered: