📄️ Notification Settings
Navigate to Edit monitor page and scroll to Notification Settings section to change how the monitor specific notifications should be sent.
📄️ Change Schedule
Monitors can be setup to run automatically at configured scheduled intervals. To change the monitoring schedule:
📄️ Monitoring Alerts
Monitors can send alerts for FAILURES, WARNINGS and RECOVERY scenarios. In order to cut down the noise due to repeat failures for monitors, we do not send alerts for all failure scenarios. The rules below apply to Email, Slack, Teams notifications and all other monitor related integrations.
📄️ Snooze Alerts
Alert notifications for a monitor can be snoozed to prevent dispatch of failure, warn and recovery notifications for a monitor. Snoozing notifications will help reduce noise during maintenance windows, when the monitoring script is unstable or when a failure is expected for a monitor.
📄️ Monitoring results
When a monitor is configured to run from multiple monitoring locations, the results from all the locations are evaluated to determine the final outcome.
📄️ Data Retention
All Workspaces setup under Limited Preview plan or Free plan will have a maximum data retention period of 10 days. Any monitoring results and associated data will be automatically deleted after this interval.
📄️ Security recommendations
We recommend the following general security practices when setting up DevRaven for monitoring your services. These recommendations are not just specific to DevRaven, but can apply to any monitoring services you use.
📄️ Monitoring Locations
We support running monitors from the following locations:
📄️ Distributed Tracing
When a user performs an operation in a web application, there might be multiple backend services operating in concert to support that functionality. Often times in microservices, it can be hard to identify the exact source of a failure.