Hello, this is Toya (
id:KGA), CRE of the Mackerel team. I would like to inform you of the contents of this update.
- You can now select stacked graphs even for query graphs with labeled metrics.
- The organization display name will now also be shown in alert notifications to Slack, etc., and in the browser title.
- The deadline when inviting a user to an organization has been extended to 7 days.
- More metrics can be obtained through linking with RDS or Aurora in AWS integration.
- Fixed an issue in which it was not possible to obtain any system data if loading file system data failed in the Windows version of mackerel-agent.
- Updated mackerel-plugin-redis and mackerel-plugin snmp.
You can now select stacked graphs even for query graphs with labeled metrics.
Labeled metrics became public beta since March 2024, and you can now select stacked graphs as the display format when displaying query graphs on the custom dashboard.
Please see the article below regarding labeled metrics (compatible with OpenTelemetry), and take advantage of it.
The organization display name will now also be shown in alert notifications to Slack, etc., and in the browser title.
As shown in the screenshot below, the organization display name will now also be shown in alert notifications to Slack, Chatwork, or Microsoft Teams, etc., and in the browser title. This makes it easier to understand the organization when you receive an alert notification or have multiple tabs open, etc.
Please see the announcement article below for information on the organization display name.
The deadline when inviting a user to an organization has been extended to 7 days.
Before this, the deadline when inviting a user to an organization was 3 days, and the deadline would often expire without the invited user noticing the invitation, etc. This deadline has been extended from 3 days to 7 days, allowing you to invite users to an organization with ample time to spare.
Please see the help article below for information on the other methods for inviting users to an organization.
More metrics can be obtained through linking with RDS or Aurora in AWS integration.
As shown in the chart below, more metrics can be obtained through linking with RDS or Aurora in AWS integration. Please note that this may cause the default number of metrics obtained on a single host to exceed the host metrics limit. Please see the page below for information about the calculation of charges when the metrics limit is exceeded.
- Handling of host conversion when plan limits are exceeded – Mackerel Support
- How usage fees are calculated (starting November 1st, 2024) – Mackerel Support
Please see the help article below for the details on metrics obtainable with RDS or Aurora, including those that are newly obtainable with this update.
There is also a setting to choose to enable or disable automatically adding new AWS integration metrics, so please take advantage of that as well.
New metrics now obtainable with both RDS and Aurora
| Graph name | Metric | Metric name in Mackerel |
|---|---|---|
| Checkpoint Lag | CheckpointLag | rds.checkpoint_lag.lag |
| Connection Attempts | ConnectionAttempts | rds.connection_attempts.count |
| CPU Surplus Credits | CPUSurplusCreditBalance CPUSurplusCreditsCharged |
rds.cpu_surplus_credits.balance rds.cpu_surplus_credits.charged |
| EBS Balance | EBSByteBalance% EBSIOBalance% |
rds.ebs_balance.byte rds.ebs_balance.io |
| Log Volume Disk Queue | DiskQueueDepthLogVolume | rds.log_volume_disk_queue.depth |
| Log Volume Free Storage Space | FreeStorageSpaceLogVolume | rds.log_volume_disk.free |
| Log Volume IOPS | ReadIOPSLogVolume WriteIOPSLogVolume |
rds.log_volume_iops.read rds.log_volume_iops.write |
| Log Volume Latency | ReadLatencyLogVolume WriteLatencyLogVolume |
rds.log_volume_latency.read rds.log_volume_latency.write |
| Log Volume Throughput | ReadThroughputLogVolume WriteThroughputLogVolume |
rds.log_volume_throughput.read rds.log_volume_throughput.write |
New metrics now obtainable with RDS
The replication channel name goes in the metric named CHANNEL_NAME.
| Graph name | Metric | Metric name in Mackerel |
|---|---|---|
| Replication Channel Lag | ReplicationChannelLag | rds.replication_channel_lag.CHANNEL_NAME |
Metrics which were only obtainable with RDS that can now be obtained with Aurora as well
| Graph name | Metric | Metric name in Mackerel |
|---|---|---|
| Disk IOPS | ReadIOPS WriteIOPS |
rds.diskiops.read rds.diskiops.write |
Fixed an issue in which it was not possible to obtain any system data if loading file system data failed in the Windows version of mackerel-agent.
Before this, it was not possible to obtain any system data if loading even a single piece of file system data failed in the Windows version of mackerel-agent. However, we have improved this behavior, so that when obtaining data and metrics for a given file system fails, it will skip that file system, and obtain the data for another file system.
This feature is available in mackerel-agent v0.81.0 and later.
Updated mackerel-plugin-redis and mackerel-plugin snmp.
- mackerel-plugin-redis
- You can now designate the
usernameparameter when connecting to Redis. - This update was contributed by users! Thank you very much!
- You can now designate the
- mackerel-plugin-snmp
- When SNMP metrics are received as text strings, they can now also be parsed as numeric values.
These features are available in mackerel-agent-plugins v0.82.0 and later.
