-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Deprecating Oracle Python integration (DBMON-3776) #22299
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
Conversation
Preview links (active after the
|
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.
Review is in progress, but I'd like to leave this open and take a look at the changes to the main integration page before I review further. That way we can cut down on duplication (and I can get a clearer idea of how we should document this :) )
Co-authored-by: Heston Hoffman <heston.hoffman@datadoghq.com>
Co-authored-by: Heston Hoffman <heston.hoffman@datadoghq.com>
Co-authored-by: Heston Hoffman <heston.hoffman@datadoghq.com>
| 3. Once configured, you can create a [monitor][10] based on `oracle.custom_query.locks` metrics. | ||
| ## Data Collected |
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.
The "Data Collected" section feels out of scope for the page, I recommend deleting it. They can read about the integration on its dedicated page.
Co-authored-by: jhgilbert <jen.gilbert@datadoghq.com>
What does this PR do? What is the motivation?
The Oracle Python integration will be deprecated in the next Agent release. This document preserves the configuration steps for the older Agent releases.
Merge instructions
Additional notes