Skip to content
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

[Oracle Module] Change tablespace metricset collection period #30948

Closed
Tracked by #30810
andresrc opened this issue Mar 22, 2022 · 0 comments · Fixed by #31259
Closed
Tracked by #30810

[Oracle Module] Change tablespace metricset collection period #30948

andresrc opened this issue Mar 22, 2022 · 0 comments · Fixed by #31259
Assignees
Labels
Team:Service-Integrations Label for the Service Integrations team

Comments

@andresrc
Copy link
Contributor

Problem

  • Oracle DBAs typically look at the growth or reduction of their table space and disk space over long periods of time. It's just wasted performance and overkill to pull those statistics every 10 seconds. All DBAs are interested in is answering this is how much space was allocated and out of that space, this is how much has been used up. These numbers don’t change drastically. If there is a problem with the space allocation, all bells and whistles will go off way before anything goes wrong.

Solution

  • Give the users the ability to change the collection interval however they want to. And keep the default value as high as 10 minutes or maybe more as a recommendation so that first-time users don’t waste cycles and resources.

User Stories

  • As an Oracle DBA Elastic user, I want Elastic to provide default collection intervals of 60 seconds or more and warn users if they change the collection frequency to be less than 60 seconds so that users don’t accidentally impact their databases and witness performance issues as the first impression.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Service-Integrations Label for the Service Integrations team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants