-
Notifications
You must be signed in to change notification settings - Fork 523
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 event.outcome to transactions and spans #4064
Conversation
💔 Build FailedExpand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
21be456
to
318f9cf
Compare
e3fcb7b
to
a4abbb2
Compare
3219c30
to
50aca18
Compare
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Note to reviewer: you might want to filter out the |
An agent implementation can be found here: elastic/apm-agent-python#899 |
Thanks @beniwohli. I tested with apm-agent-python & aiohttp, and it appears to be working well: |
* spec: add {transaction,span}.outcome * model: add {Span,Transaction}.Outcome fields * model/modeldecoder: {span,transaction}.outcome * Update fields, tests, generated docs * Add changelog entry
Motivation/summary
This PR adds
outcome
as a field oftransaction
andspan
. For RUM v3,outcome
is abbreviated too
.The value will be recorded as the
event.outcome
in the event documents, and will be used for calculating error rates.Checklist
I have considered changes for:
- [ ] logging (add log lines, choose appropriate log selector, etc.)- [ ] metrics and monitoring (create issue for Kibana team to add metrics to visualizations, e.g. Kibana#44001)- [ ] telemetryHow to test these changes
Cannot be manually tested until we have a modified agent.
Related issues
elastic/apm#299