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

Alerting needs to be implemented for ClearlyDefined #7

Open
brphelps opened this issue Mar 7, 2020 · 1 comment
Open

Alerting needs to be implemented for ClearlyDefined #7

brphelps opened this issue Mar 7, 2020 · 1 comment

Comments

@brphelps
Copy link
Contributor

brphelps commented Mar 7, 2020

Per Gene:

For the alerts, besides the regular stuff, Azure Search indexer should be monitored for errors, Redis should be monitored for max capacity, CosmosDB should be monitored for any errors. Crawlers should be monitored for the disk space and CPU. We have the monitoring in place for the number of messages in the queues and curation failures. Availability alerts should be added to.

@brphelps brphelps changed the title Availability alerts need to be triaged, they "maybe" exist Alerting needs to be implemented for ClearlyDefined Mar 9, 2020
@brphelps
Copy link
Contributor Author

This also should encompass getting rid of the ospocore group -- places that used it before for MSFT's specifically provisioned crawler VMs should instead use [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant