Monitoring outbox observability #1079
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
StefanHenke
commented
Jul 2, 2024
| @@ -370,6 +370,31 @@ By default, instrumentations for CAP-specific components are disabled, so that n | |||
|
|
|||
| For specific steps to change the log level, please refer to the respective section for [configuring logging](#logging-configuration). | |||
|
|
|||
|
|
|||
| #### Transactional Outbox | |||
There was a problem hiding this comment.
I would rather propose to restructure the headers. Unfortunately, we are already on level 4 because of which I would avoid to introduce level 5.
I would propose to group the CAP-specific things according to the signal. Main motivation is that e.g. for the outbox we also have spans and traces already today and we have natural overlaps:
### CAP Instrumentation for Traces
By default, instrumentations ....
### CAP Instrumentation for Metrics
| @@ -359,7 +359,7 @@ The following steps describe the required configuration: | |||
| By default, instrumentations for CAP-specific components are disabled, so that no traces and spans are created even if the Open Telemetry Java Agent has been configured. It's possible to selectively activate specific spans by changing the log level for a component. | |||
There was a problem hiding this comment.
CAP Java provides additional instrumentations for traces and spans which covers CAP-specific components. It´s possible to selectively activate or deactivate specific spans by changing the log level for a component.
Co-authored-by: Stefan Henke <[email protected]>
Co-authored-by: Stefan Henke <[email protected]>
Co-authored-by: Stefan Henke <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.