-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Support performance/APM features #426
Comments
It’s something I’ve definitely been keeping an eye on. Now that it’s released, I’ll be trying to get some proofs of concept together. |
Is there anything the community can do to help? |
Good question, thanks for asking it! Once I have a better handle on the structure, I’ll create issues around the features which should be a great place for contributions 🙂 |
It turns out that before this can happen I will need to make some bigger changes to move existing functionality to the new Unified API and Envelope data format, so I'll be tackling that first. |
I wonder if a good MVP would be just to have the ability to send metrics to Sentry. We can manually hook up telemetry since Phoenix, Ecto, etc. have good telemetry support. |
Waiting for this feature :) |
It's an exciting feature that's at the top of my list for support! Ruby's conversion to the Unified API and Envelope format gives a bit of an insight into what needs to happen first: https://github.com/getsentry/sentry-ruby/projects/3 This library's footprint is smaller, so it should be easier in some respects 🙂 |
Is there API specification for that? I could review the possibility to implement such feature if only there is stable API for that. I could make it a backend for Erlang's OpenTelemetry implementation. |
Apologies this is taking longer than anticipated, but I'm hoping that the holidays will give me some time to finish the partial implementation I have. @hauleth It's sort of spread across a handful of pages: https://develop.sentry.dev/sdk/event-payloads/transaction/, https://develop.sentry.dev/sdk/event-payloads/span/ have some description, but I'd be very interested in making it easier to integrate with OpenTelemetry. |
Is the APM feature available for free accounts? I don't mind to help to implement this feature, I will try to check the API. |
@speeddragon I'm not sure, I'd reach out to Sentry to see. I've been making slow progress, but not as much as I'd like 🙂 |
I'm trying to understand the request that needs to be made, I can make a successful request, but nothing appears on the Performance tab. I've testes with a JavaScript project and it works, I need to check what is missing in my HTTP request. If I make some progress I will reply back. EDIT: Finally made a successful request via Postman. I will try to integrate that with this repo. |
Sentry is adopting OpenTelemetry in general, right? It doesn't cover all Sentry features at this time but starting with tracing and using the OpenTelemetry Erlang/Elixir lib for this would mean many more people involved in helping move it forward and a shared base. You, or anyone reading this interested in these Sentry features for Elixir, should check out the Observability Working Group of the Erlang Ecosystem Foundation https://erlef.org/wg/observability and the Erlang/Elixir OpenTelemetry SIG https://github.com/open-telemetry/community#special-interest-groups |
Is there any update on support for tracing? We're wanting to migrate from NewRelic to Sentry, and in our POC, we see the |
We are currently using Sentry for distributed tracing, and it works reasonably well with some caveats. The details of the setup can be found in the blog post. |
@ananthakumaran nice. If you want it'd be great to get the propagator added to https://github.com/open-telemetry/opentelemetry-erlang-contrib/ |
any updates on this @mitchellhenke ? |
Closing this in favor of a single issue about APM, that is, #538. |
Does this project plan to add support for Sentry's performance/APM features? Elixir's/Erlang's telemetry support seems like a perfect fit for this.
The text was updated successfully, but these errors were encountered: