Update AnalyticsDataPublisher to Handle Multiple Reporter Types #12580
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.
Purpose
To improve the flexibility of APIM analytics by allowing users to configure multiple reporter types. Previously, it was limited to a single reporter type specified in the configuration, defaulting to Choreo analytics if not explicitly set. This PR enables users to setup multiple analytics reporters simultaneously.
Issues
Fixes wso2/api-manager#3099
Approach
The new implementation allows for multiple loggers to be enabled through configuration in the
deployment.toml
file. Users can now specify an array of reporter types, which the system will process and initialize accordingly.Configuration Examples
Enable both Choreo and ELK analytics:
In this case,
type = "choreo, elk"
is also allowed.Enable only ELK analytics:
In this case,
type = "elk"
is also allowed.Default behavior (Choreo analytics) when type is not defined:
Maintainers: Check before merge