In error-tracking.md the definition of how outcome is set contradicted what we define in tracing-transactions.md and in tracing-spans.md, especially the following:
Tracking an error that's related to a transaction does not impact its outcome.
This PR changes error-tracking.md to make it match the outcome definition from other parts of the spec (see links above). I think most agents already do this according to tracing-transactions.md and tracing-spans.md - so I expect we won't need to change any implementation in a specific agent.
If that's not the case, please raise it and let's discuss.
[x] Create PR as draft
[ ] Approval by at least one other agent
[ ] Mark as Ready for Review (automatically requests reviews from all agents and PM via CODEOWNERS)
Remove PM from reviewers if impact on product is negligible
Remove agents from reviewers if the change is not relevant for them
[ ] Merge after 2 business days passed without objections \
To auto-merge the PR, add /schedule YYYY-MM-DD to the PR description.
In
error-tracking.mdthe definition of howoutcomeis set contradicted what we define in tracing-transactions.md and in tracing-spans.md, especially the following:This PR changes
error-tracking.mdto make it match theoutcomedefinition from other parts of the spec (see links above). I think most agents already do this according to tracing-transactions.md and tracing-spans.md - so I expect we won't need to change any implementation in a specific agent.If that's not the case, please raise it and let's discuss.
CODEOWNERS)/schedule YYYY-MM-DDto the PR description.