-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add exceptionmetricsprocessor #17271
Conversation
@marctc, thanks for the contribution. Please read through the guidelines for contributing a component. The most important point is that you'll need to open an issue to propose the component, with the goal of finding a "sponsor" (a maintainer or approver who is willing to co-own the component). For what it's worth, I think a component like this makes sense, but we will probably want it implemented as a "connector". (See open-telemetry/opentelemetry-collector#6700) |
@djaglowski thanks for the info! I created the issue here: #17272. I'm reading the contributing guidelines for the mising steps. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Description: Added processor to create metrics from recorded exceptions. The implementation
is heavily inspired from spanmetricsprocessor.
Link to tracking Issue: #17272
Note for reviewers: Does it make sense to reuse some of the functions from
spanmetricsprocessor
thatare duplicated here? Or would it be better to do some refactorings and extract common files/functions in a separate
directory?
Documentation: Added examples in README.