Hello. CRE Miura (id:missasan) here.
For a long time now we’ve been receiving many enthusiastic requests to release a downtime function that allows the user to stop monitoring at a specified time!
Leading up until now, Mackerel has had several functions for suspending monitoring or notifications, but in order to respond to scheduled batches and maintenance etc., the use of a separate scheduler function was required like with cron for LinuxOS, taking time and effort. With the release of this downtime feature, it is now possible to set up flexible schedules from Mackerel. And of course, it can also be configured from the API.
The Mackerel team is pleased to be able to provide a function that is directly connected to saving users time and effort. In addition to this, if there are changes that you would like to see made to other functions, please feel free to send us some feedback at【email@example.com】. For open source related items, pull requests are also welcome!
Now on to this week’s update information.
Downtime feature release
We’ve released a function that allows you to suspend monitoring for a specified time period, for a target service/role or monitor. Recurrence settings such as hourly, daily, weekly (day of the week), monthly, and yearly are also available.
During the downtime’s configured time period, incidents will not appear on the alert list nor will notifications be sent to the notification channel, even if there are metric posts that conflict with the target monitor. (Metrics will be posted)
As described in the following use cases, this can be used in advance for load increases or for instances when the service is known to stop.
- Periodic batch processing
- Scheduled maintenance periods
How to use
Downtime can be configured in the following two ways.
- From the console screen
- From the API
For more detailed information, check out the help page below.
Alert Group Settings API release
Alert Group Settings can now be obtained, created, updated, and deleted from the API.
For more details, check out the help page below.
WebSocket related metrics can now be obtained. Check out the following help page for more details regarding obtainable metrics.
mackerel-plugin-solr now supports retrieving metrics for Apache Solr 7.x and 8.x
With mackerel-agent-plugins v0.58.0, Apache Solr 7.x and 8.x metrics can now be obtained in addition to the previously obtainable 5.x and 6.x.
-redis-namespace option added to mackerel-plugin-sidekiq
Also in mackerel-agent-plugins v0.58.0, the
-redis-namespace option has been added to mackerel-plugin-sidekiq, and the key namespace can now be specified. If you use a gem like redis-namespace to give the Redis key a namespace, you can now get metrics by specifying this option.