Mackerel blog #mackerelio

The Official Blog of Mackerel

The official release of Anomaly Detection for roles and more

Hello. CRE Miura (id:missasan) here.

This week is packed full of new announcements like the official release of Anomaly Detection for roles, AWS Integration support for Amazon Kinesis Data Firehose, OSS updates, and the Obon holiday break... so be sure to read until the end!

Now on to this week’s update information.

The official release of Anomaly Detection for roles

The Anomaly Detection for roles function has officially been released. With this, as was previously announced the other day, usage of this function will incur charges starting from August 2019. The ability to check the functions usage status will be available from the Plan tab in your organization’s detail screen starting early August.

Check out the following blog post for more information about billing.

mackerel.io

The following features have also been released.

Support for Mackerel API

Anomaly Detection for roles can now be operated from the Mackerel API. This can be used with the Monitor configuration API and the Alerts API.

mackerel.io

Support for mkr command

With mkr v0.39.0, Anomaly Detection for roles can now also be operated from mkr command.

With a monitor configured for Anomaly Detection for roles, monitor information and alerts will be displayed in the mkr monitors and mkr alerts results. Configuration changes with the diff, push, and pull subcommands are also supported.

mackerel.io

Amazon Kinesis Data Firehose Integration release

Amazon Kinesis Data Firehose now supported with AWS Integration.

mackerel.io

When integrating with AWS integration, billable targets are determined using the conversion 1 delivery stream = 1 Micro host. Up until now, it was possible to collect metrics using the plugin if you set up a metric collection instance etc., but now with integration, it’s even easier to visualize metrics in Mackerel. Be sure to give it a try!

custom_identifier now supported with check-plugin

custom_identifier is a configuration that allows the user to assign a unique identifier to the host and can be specified in the plugin’s settings. By using this, monitoring results can be sent as a monitor of the specified host instead of the host on which mackerel-agent is running.

With mackerel-agent v0.61.1, custom_identifier can now also be used for check monitoring. For example, when using check-mysql to check the connection from the Web server to the DB server, you can post this result as that of the DB server.

For more details, check out the following help page.

mackerel.io

CGC and CGCT metrics added to plugin-jvm

With mackerel-agent-plugins v0.57.0, CGC and CGCT metrics have been added to mackerel-plugin-jvm. This also addresses the metric retrieval error issue when using SerialGC.

github.com

Support Window closed during the Obon holiday from August 13th-15th

Official Mackerel support (the "Feedback" option displayed in the upper right corner of the header while logged-in to Mackerel as well as correspondence/inquiries to support@mackerel.io) will be closed during the Obon holiday through the following dates.

Support window period of closure:Aug. 13th, 2019 (Tues.) ~ Aug. 15th, 2019 (Thur.) (JST)

Inquiries received during this period will be replied to in order on Friday, August 16th. Thank you for your cooperation.