Hello! This is Toya (
id:KGA) from the Mackerel CRE team. I'm pleased to share the details of this update.
- Client tokens for posting traces from web frontends and mobile apps now available
- Remaining time until snooze release is now visible for trace issue notifications
- Slack notification settings for trace issues have been moved under the Issues list
- Azure Front Door metrics are now available via the Azure integration
- You can now filter by organization name or display name in the Organizations list
- Host display name is now shown in the page title on the Host Details screen
- Changed the rendering font for graph images
- Released terraform-provider-mackerel v0.9.0
Client tokens for posting traces from web frontends and mobile apps now available
Mackerel's API keys are primarily intended for server-side use and were not suitable for use on the client side, such as in web frontends or mobile apps. To address this, we have released client tokens designed specifically for posting traces from the client side. Since client tokens are dedicated solely to trace posting, they can be safely embedded in end-user-facing applications without granting unnecessary permissions.
Client tokens can be created from the "Client Tokens" tab in the dashboard. For more details, please refer to the Client Tokens help page.
Remaining time until snooze release is now visible for trace issue notifications
Previously, after snoozing notifications for a trace issue, there was no way to check how much time remained until notifications would resume. With this update, the remaining time until snooze release is now displayed for trace issues.
Clicking "Unsnooze" will cancel the snooze and resume notifications.
Slack notification settings for trace issues have been moved under the Issues list
The Slack notification settings for trace issues have been moved from the legacy Traces settings page to under the Issues list.
Azure Front Door metrics are now available via the Azure integration
You can now retrieve metrics for Azure Front Door, Azure's CDN service, through the Azure integration. This enables you to monitor and track the performance and availability of your CDN using Mackerel. Each Azure Front Door profile is counted as 1 micro host. For details on the available metrics, please refer to the help page.
You can now filter by organization name or display name in the Organizations list
You can now filter by organization name or display name on the Organizations list page. This makes it easier to find the organization you're looking for.
Host display name is now shown in the page title on the Host Details screen
When a display name is set for a host, it is now shown in the page title on the Host Details screen. This makes it easier to identify which host's details you are viewing when managing multiple hosts.
Changed the rendering font for graph images
We have changed the font used for rendering graph images. This ensures that non-ASCII characters such as Japanese in graph definition names or metric names are now displayed correctly. This change affects graph images displayed in the following areas:
- Embedded graphs: SVG/PNG images for
<iframe>embedding generated through the graph sharing feature - Graph image downloads: Images downloaded through the graph sharing feature
Released terraform-provider-mackerel v0.9.0
We have released v0.9.0 of terraform-provider-mackerel. The main changes are as follows:
- The minimum supported Terraform version has been changed to v1.0
- URLs for Slack and Webhook notification channels are now treated as Sensitive
- Auto-retirement for ALB/NLB is now supported in AWS Integration
The first two of these include breaking changes.
Due to the minimum Terraform version change, this release is not compatible with older versions of Terraform. Please upgrade Terraform to v1.0 or later before using this version. Additionally, making Slack and Webhook notification channel URLs sensitive may require modifications to existing Terraform configurations.
This change was contributed by user @mkusaka. Thank you!
Please note that after upgrading the provider, the first terraform plan for existing resources may show an update-in-place diff once. This will be resolved by running terraform apply.
For detailed compatibility changes and migration notes, please also check the v0.9.0 release page.
