Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developer Experience Survey #770

Open
tsloughter opened this issue Sep 13, 2024 · 2 comments
Open

Developer Experience Survey #770

tsloughter opened this issue Sep 13, 2024 · 2 comments
Labels
question Further information is requested

Comments

@tsloughter
Copy link
Member

For the DevEx SIG (https://github.com/open-telemetry/sig-developer-experience/) we are doing a survey of languages and their differences from the spec along with what users are asking for. I can fill in discrepancies and extra convienciences but realized I should actually open this up to the community in case I miss any requested features and things you like from other telemetry projects in Erlang/Elixir:

  • differences from upstream spec:
    • discrepancies - why?
    • extra convenience
  • most requested features
    • API
    • SDK
    • Instrumentations/semantic conventions
  • things to consider from other telemetry projects in Erlang/Elixir
@tsloughter tsloughter added the question Further information is requested label Sep 13, 2024
@nathanl
Copy link

nathanl commented Sep 13, 2024

I'm working on a project where we already collect some in-memory metrics in LiveDashboard and would like to start storing them somewhere to report on over time. Spans and traces would be a good later step for us.

Maybe this is the wrong place to look, but according to https://opentelemetry.io/docs/languages/erlang/instrumentation/#metrics

The metrics API, found in apps/opentelemetry_experimental_api of the opentelemetry-erlang repository, is currently unstable, documentation TBA.
The logs API, found in apps/opentelemetry_experimental_api of the opentelemetry-erlang repository, is currently unstable, documentation TBA.

I'd really like otel to be our solution for shipping all three things to a backend. Bonus if there were support for DataDog - I know not everyone likes it, but it's a favorite tool for our infra team, and we already ship our logs there (via other means).

@tsloughter
Copy link
Member Author

@nathanl sorry, the survey wasn't clear about "most requested", this is actually about things requested that are outside the spec.

Metrics will be reviewed by the Technical Committee so they can go stable and moved into the main API/SDK applications (opentelemetry/opentelemetry_api) as soon as I have time to write up some docs/getting started so they have a starting place to do a review.

Datadog is supported either through the otel collector: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/datadogexporter or the datadog agent which accepts OTLP https://docs.datadoghq.com/opentelemetry/interoperability/otlp_ingest_in_the_agent/?tab=host

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants