Any scheduled maintenance that involves a suspension of the Mackerel service will be sent via our blog and newsletter.

Regardless of your email notification settings, all users registered in Mackerel will be sent a notification so please be sure to check.

The following restrictions may occur during the maintenance period.

Additionally, changes or additions may be made, so please be sure to check the announcements for details.

• The maintenance work finish time will be the latest expected finishing time. If the actual maintenance work is completed earlier, our systems will be restarted at the earlier time.
  • We will notify you once the maintenance work has been completed and all systems have been tested.
• Once the maintenance work is started, all Mackerel systems will be stopped for a short period of time.
  • Mackerel web access, agent data submissions, API access (including the CLI tool), alert notifications, etc. will become unavailable.
• Metrics and check monitoring results collected by the agent are buffered on the agent side during maintenance and resent after maintenance is complete.
  • If the data is sent successfully, graphs will also be displayed for the time period of the maintenance work.
  • Please note that restarting or pausing a agent before the data is resent will cause it to lose all its buffered data.
  • Starting up a agent during the maintenance period will fail, as all communications with the main Mackerel system will be blocked.
  • During the maintenance period, all data sent to Mackerel will fail. Error messages to this effect will be output to the error logs.
  • If the metric exceeds the monitoring threshold during maintenance and then falls below the threshold, no alert will be generated after maintenance is complete.
  • Check monitoring alerts that occurred during maintenance will be sent out all at once after maintenance is complete, up to 6 hours worth.
    • The alert occurrence and recovery times are the times posted to Mackerel.
• Post of labeled metrics by the OpenTelemetry Collector is not buffered, but it is possible to use the metric submission retry setting to repost metrics that fail to post.
  • Please note that restarting or stopping the OpenTelemetry Collector before the metric post is complete will result in the loss of data held for metric post.
  • OpenTelemetry Collector can be started during maintenance, but fails to post metrics to Mackerel.
  • During the maintenance period, all data sent to Mackerel will fail. Error messages to this effect will be output to the error logs.
  • If the metric exceeds the monitoring threshold during maintenance and then falls below the threshold, no alert will be generated after maintenance is complete.
• External monitoring or cloud integration graphs may have missing data corresponding to the maintenance period.