Hello! This is Sudo (
id:do-su-0805) from the Mackerel CRE team. Here are our latest updates.
- New variables have been added for use with the Metric Explorer
- In a host's network information, if a single interface has duplicate IP addresses, they will now be combined into one
- When mkr plugin install is run without specifying a version, the GitHub API will no longer be used to determine the latest version
- Warning: Support for AWS WAF Classic with AWS integration will end on Friday, September 26th, 2025
New variables have been added for use with the Metric Explorer
Two new variables, $__interval and $__rate_interval, are now available when you use PromQL with the Metric Explorer.
$__interval: Indicates the metric granularity corresponding to the graph's display period. For example, if metrics are displayed at one-minute intervals, this will be one minute.$__rate_interval: A value significantly larger than$__interval. Calculations can continue even with temporary data loss.
Using these variables eliminates the need to specify fixed values for calculations with functions like irate(). This allows for smooth calculations for any display period and prevents the error message "There is no data for the selected period."
In a host's network information, if a single interface has duplicate IP addresses, they will now be combined into one
You can view network information for a host in Mackerel as part of "Host Info". Previously, if the same IP address had been set multiple times for a single interface, it would show the number that had been set. Now, these are combined and shown as one.
This change affects the "Network" information on the host details screen as well as responses to host information retrievals via the API.
When mkr plugin install is run without specifying a version, the GitHub API will no longer be used to determine the latest version
mkr plugin install can be used to install plugins released on GitHub.com that meet the specifications.
When no release tag was specified during installation, the latest release version would be retrieved, and the GitHub API would be used to check for the latest version.
However, large numbers of requests generated by device provisioning or other such tasks would sometimes run into the GitHub API's rate limit, resulting in failure.
This fix makes it so that, instead of the GitHub API being used, the the latest version will be checked by accessing releases/latest as described on the help page below.
Linking to releases - GitHub Docs
This will prevent failures due to rate limits when a large number of requests is generated.
If retrieval by this method fails, the system will fall back to the previous method using the GitHub API.
This fix was contributed by @kazeburo. Thank you!
Warning: Support for AWS WAF Classic with AWS integration will end on Friday, September 26th, 2025
As we warned in our announcement of July 25th, 2025, the end of support for AWS WAF Classic with AWS integration will be on Friday, September 26th, 2025.
Starting Friday, September 26th, 2025, you will no longer be able to add AWS WAF Classic hosts or retrieve metrics using AWS integration.
As previously stated, it will still be possible to monitor AWS WAF even after support for AWS WAF Classic ends. Some of you may have already migrated to AWS WAF, but for those of you who are still monitoring with AWS WAF Classic, we ask that you migrate to AWS WAF.
