Hello. Mackerel team CRE Inoue (id:a-know) here with another update announcement.
New metric targets added for AWS / NLB Integration
- Processed Bytes
- Established Active Flow
- Consumed LCUs
- New Flow
- TLS Negotiation Error
In addition to this, the maximum number of retrievable metrics has been increased from
6 + 2 × (number of target groups) to
21 + 2 × (number of target groups). So depending on the number of target groups, you may exceed the 30 metric limit in which case the excess will be converted into an additional micro host (FAQ・Handling of host conversion when plan limits are exceeded - Mackerel Docs).
Obtaining metrics with AWS Integration can be freely configured at your own discretion in settings. Although, metrics are retrieved by default, so please manage this as necessary.
aws.amazon.com (Japanese only)
With this update, it is now possible to monitor
HTTP Protocol-Type API Gateway resources. Prior to this, only
WebSocket were supported, but now all currently existing Protocol-Type are available.
For more on integratable metrics, check out the documentation linked below.
Reflect a selected metric when sharing service metric graphs to notification channels
Have you ever used the graph sharing function that lets you post graphs to notification channels by clicking the camera icon located in the upper right corner of each graph?
Now, when sharing service metric graphs, you can select a particular metric to be reflected in the shared content.
This feature has been supported for system metrics and custom metrics, but is now available for service metric graphs as well. We hope this will be helpful for communicating and addressing specific areas.