You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
brphelps
changed the title
Availability alerts need to be triaged, they "maybe" exist
Alerting needs to be implemented for ClearlyDefined
Mar 9, 2020
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]
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.
The text was updated successfully, but these errors were encountered: