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

[RFE] New CPU & memory detectors for App Service Plan #249

Open
BzSpi opened this issue Feb 19, 2021 · 0 comments
Open

[RFE] New CPU & memory detectors for App Service Plan #249

BzSpi opened this issue Feb 19, 2021 · 0 comments
Labels
detectors About nex or existing detectors new feature Request for new feature
Projects

Comments

@BzSpi
Copy link
Contributor

BzSpi commented Feb 19, 2021

What is the module?
integration_azure-app-service-plan

Is your feature request related to a known monitoring hole? Please describe.
Current CPU & memory detectors are configured on the Instance dimension. However, we should be able to monitor if only an instance is over-used (with high thresholds) and also if the average CPU & memory usage is high on the whole service.
Those 2 detectors have different remediation tasks. Either fix the unhealthy instance or scale the service.

Describe the solution you'd like
Having two sets of detectors with different dimensions and thresholds for memory & CPU.

@BzSpi BzSpi added detectors About nex or existing detectors new feature Request for new feature labels Feb 19, 2021
@xp-1000 xp-1000 added this to To do in Claranet via automation Feb 19, 2021
@xp-1000 xp-1000 changed the title [RFE] New detector ... for module ... [RFE] New module for integration_azure-app-service-plan Feb 19, 2021
@BzSpi BzSpi changed the title [RFE] New module for integration_azure-app-service-plan [RFE] New CPU & memory detectors for App Service Plan Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
detectors About nex or existing detectors new feature Request for new feature
Projects
Development

No branches or pull requests

1 participant