-
Notifications
You must be signed in to change notification settings - Fork 387
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
[O11y][Oracle WebLogic] Add dimension fields for threadpool datastream #7517
[O11y][Oracle WebLogic] Add dimension fields for threadpool datastream #7517
Conversation
🌐 Coverage report
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
packages/oracle_weblogic/data_stream/threadpool/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Please complete peer review additionally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…into oracle_weblogic-threadpool-add-dimension Conflicts: packages/oracle_weblogic/changelog.yml packages/oracle_weblogic/manifest.yml
Package oracle_weblogic - 1.1.2 containing this change is available at https://epr.elastic.co/search?package=oracle_weblogic |
Marked done in the project. |
What does this PR do?
This PR adds dimension fields for threadpool datastream to support TSDB enablement.
Issue: In the ThreadPool datastream, the data collection is performed by Jolokia input and there are different MBeans used to perform data collection. Because of different MBeans, multiple events are generated at the same time. And I don't have found any possible unique identifier field in fields.yml file for threadpool datastream. Hence the data was getting dropped while performing the data collection because of getting multiple events at the same time.
Possible Solution: To overcome the above issue, I have introduced a unique identifier called
oracle_weblogic.threadpool.mbean
that represents the value of the doc that is collected from the particular MBean and makes it dimension true.Checklist
I have reviewed tips for building integrations and this pull request is aligned with them.
I have verified that all data streams collect metrics or logs.
I have added an entry to my package's
changelog.yml
file.I have verified that Kibana version constraints are current according to guidelines.
Relates Oracle WebLogic TSDB Enablement #7512
Screenshot
Refer: #7512