Elastic Search is needed for the dynamic monetization plan
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Current Limitation
When executing the Monetization Usage Publish job via the Admin REST API as per the documentation a NullPointerException is thrown if the WSO2 API Manager cannot successfully retrieve usage data from the configured Elasticsearch instance.
Instead of handling the null response gracefully and logging a descriptive error (e.g., "Failed to connect to Elasticsearch" or "No usage data returned"), the MonetizationUsagePublishAgent crashes when attempting to read the null byte array into a String.
Environment:
Product Version: WSO2 API Manager 4.7.0-m2
Analytics Engine: Elasticsearch (ELK)
Monetization Engine: Stripe (org.wso2.apim.monetization.impl.StripeMonetizationImpl)
Suggested Improvement
Update the documentation to include the elastic search before configuring dynamic business plan.
Version
4.7.0-m2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked API monetization documentation and review the steps around configuring the dynamic business plan and sending usage data to the billing engine. Update the documented sequence to include Elasticsearch before dynamic business-plan configuration, and verify that the prerequisite is clear to someone following the page from the start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100