-
Notifications
You must be signed in to change notification settings - Fork 19
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
feat: capture message attributes for flow logs #79
Merged
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
…ow level logging is enabled
manikmagar
reviewed
Dec 12, 2024
.../avioconsulting/mule/logger/internal/listeners/CustomLoggerAbstractNotificationListener.java
Outdated
Show resolved
Hide resolved
manikmagar
reviewed
Dec 19, 2024
src/main/java/com/avioconsulting/mule/logger/internal/config/CustomLoggerConfiguration.java
Outdated
Show resolved
Hide resolved
.../avioconsulting/mule/logger/internal/listeners/CustomLoggerAbstractNotificationListener.java
Outdated
Show resolved
Hide resolved
.../avioconsulting/mule/logger/internal/listeners/CustomLoggerAbstractNotificationListener.java
Outdated
Show resolved
Hide resolved
.../avioconsulting/mule/logger/internal/listeners/CustomLoggerPipelineNotificationListener.java
Outdated
Show resolved
Hide resolved
.../avioconsulting/mule/logger/internal/listeners/CustomLoggerPipelineNotificationListener.java
Outdated
Show resolved
Hide resolved
src/main/java/com/avioconsulting/mule/logger/api/processor/FlowLogConfig.java
Outdated
Show resolved
Hide resolved
src/main/java/com/avioconsulting/mule/logger/api/processor/FlowLogConfig.java
Outdated
Show resolved
Hide resolved
manikmagar
reviewed
Dec 19, 2024
src/main/java/com/avioconsulting/mule/logger/internal/config/CustomLoggerConfiguration.java
Outdated
Show resolved
Hide resolved
manikmagar
approved these changes
Dec 19, 2024
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.
Closes #78
Here's how it looks in studio
Validations:
Either "Attributes expression text" or "Message expression text" should be present while defining the flow-log-configuration
configuration xml:
<avio-logger:flow-log-configs> <avio-logger:flow-logs-config flowName="logger*" messageExpressionText="attributes.headers"/> </avio-logger:flow-log-configs>
Error handling
"One of attributesExpressionText or messageExpressionText must be defined in flow-logs-config"
How it Works
flowName
accepts wildCards either at the start or at the end examplemq-listener*
or*mq-listener
or*
for every Flow