search

honeybadger-io / honeybadger-elixir

Elixir client for Honeybadger.
MIT License
181 stars 55 forks source link

Erlang Ecosystem Foundation Observability Working Group #485

Open tsloughter opened 1 year ago

tsloughter commented 1 year ago

First, sorry for opening this as an issue when it isn't an issue, I would have used Discussions if those were enabled. But I should have opened this a long time ago. I don't think I've ever reached out to anyone working on Honeybadger's Elixir client to invite them to join us in the Observability Working Group for Erlang/Elixir, https://erlef.org/wg/observability

We don't meet again until May 4th, https://erlef.org/wg/observability/calendar, please feel free to join if anyone reading this has any interest.

I also work on the https://opentelemetry.io/ Erlang/Elixir library, https://github.com/open-telemetry/opentelemetry-erlang and would be interested in hearing if Honeybadger has looked at Otel and using it for error tracking -- focus is on tracing, metrics, logging and profiling, but I'd think there would be a way to integrate with at least the logging in order to give people a way to use 1 library and report both to their tracing/metrics service and Honeybadger for error tracking.

sorentwo commented 1 year ago

Hi @tsloughter! Thanks for reaching out.

I've maintained the HB package (intermittently) for a few years now, but I'm not privy to the HB team's plans. Perhaps @joshuap can provide some insight?

joshuap commented 1 year ago

@tsloughter @sorentwo hi! I was on traveling the past couple weeks, but I'm back now. :)

We are interested in Otel. We're also currently working on some new tooling around observability/structured logging in Honeybadger. We don't have an Otel backend yet, but we're considering it. The hybrid approach you mentioned for error tracking also sounds interesting.

I'll share the working group with our team! I'm personally interested in following the work you're doing. What's the format of the meetings?

tsloughter commented 1 year ago

Hi! There is definitely consideration of error tracking in Otel. On github there are some threads from years back about this explicitly. Right now the focus has been on how to convey errors/exceptions in traces and logs. The most recent thread you might fight of interest https://github.com/open-telemetry/opentelemetry-specification/issues/3198

Our meetings are a mix of just discussing what everyone is working on and questions from users. I've been trying to get more of the latter involved.

That's both for the Observability WG and the OpenTelemetry SIG meetings.