TIBCOSoftware / TIBCOSoftware/bw-tooling
BWCE Application || Memory Leak
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
I observed high memory and CPU usage after using Prometheus client jar and enabling "BW_PROMETHEUS_ENABLE" in the TIBCO BWCE application. the usage was much higher than with the option disabled on normal traffic and I tried the following:
- Optimize the metrics as there is a very high label cardinality in the metrics.
- Upgrade the Java Version
- Add filtration logic to filter processes and activities that I need metrics for
However no change regarding the high resources usage.
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
Start by reproducing the TIBCO BWCE application behavior with the Prometheus client jar and BW_PROMETHEUS_ENABLE enabled under normal traffic, comparing memory and CPU usage with the option disabled. Review the reported label cardinality and filtering attempts; done means identifying the cause of the resource increase and documenting a verified mitigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100