Heartbeat Monitoring
Tideways can alert you when it did not receive monitoring, profiling or error data from your servers for longer than a configured timeframe between 1 and 24 hours.
By default this alert is not activated until your project has transmitted data for 3 or 7 consecutive days (depending on volume).
You can send a notification to any of the available integrations when a heartbeat was not received in time and an incident is created
By default every project has a notification configured for all services in production environments alerting after 24 hours of missing data.
Configure Service Check Interval
-
Open the Notifications settings screen in your project
-
Click "Create Notification Rule" and select "Heartbeat Monitoring"
-
Select Services and Environments to match the alert notification rule. By default all services of the production environment match.
-
Configure "Alert me if there is no data after" by selecting one of 1 hour, 3 hours, 6 hours, 12 hours or 24 hours.
-
Select the integrations to send a notification in case an incident is created.
-
Save the Notification Rule.
Heartbeats for Transactions
You can also check the heartbeat of a transaction by configuring a check-in interval. If a transaction does not report data within the configured check-in intervals, then a notification is sent.
This can be used primarily to monitor cronjobs and background workers for activity and quickly finding out when they are not running anymore.
-
Open the "Transactions" settings in your project
-
Filter and search for transactions that you want to activate heartbeat monitoring for.
-
Open the "Edit Transaction" screen
-
Pick a check-in interval between 1 minute and 1 month and save the transaction settings.
You can configure how you get notified from the "Notification Settings" screen and changing the "Heartbeat" notification settings.