Skip to content

Conversation

@rquinio1A
Copy link
Member

Closes #244

Some logic has to be duplicated from LoggingResourceProcessor/LoggingSetupRecorder due to lack of build items.

Also Quarkus core registers a global LogCleanupFilter after named handlers initialization, so we need to implement #setFilter rather as an #addFilter.

@edeweerd1A
Copy link
Contributor

edeweerd1A commented Jul 2, 2024

Question: why is the new configuration entry Optional<String> and not Optional<List<String>>? Is it not possible to plug multiple filters?

@rquinio1A
Copy link
Member Author

Question: why is the new configuration entry Optional and not Optional<List>? Is it not possible to plug multiple filters?

The JUL API only supports one (https://docs.oracle.com/en/java/javase/21/docs/api/java.logging/java/util/logging/Handler.html#setFilter(java.util.logging.Filter) so I guess that's why Quarkus handlers did the same.
If we're ok deviating a bit from Quarkus core, we could use a CompositeFilter that combines several named filters.

Some logic has to be duplicated from LoggingResourceProcessor/LoggingSetupRecorder due to lack of build items.

Also Quarkus core registers a global LogCleanupFilter after named handlers initialization, so we need to implement #setFilter rather as an #addFilter.
@vietk
Copy link
Contributor

vietk commented Jul 5, 2024

Seems good for me

@vietk vietk merged commit b6573b4 into quarkiverse:main Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add quarkus.log.handler.splunk.filter

3 participants