Hello. Mackerel team CRE Inoue (id:a-know) here with another update announcement.
Billing data can now be monitored with AWS Integration
We’ve recently confirmed the occurrence of hosts being registered in Mackerel, but not posting graphs if the budgets name is longer than a certain length on the AWS side.
We apologize for the inconvenience and appreciate your cooperation as we proceed with further investigation to resolve this event.
End of Postscript
It is now possible to monitor Billing data with AWS Integration. With this, you can now monitor/visualize billing and budget metrics for your AWS account. If using AWS Organizations for consolidated billing, you can also retrieve metrics for billing amounts per member account. Prices are calculated using the conversion 1 management account = 1 micro host.
Account IDs are used for host names. And Budget names are incorporated as part of metric names, but because Japanese characters cannot be used for metric names in Mackerel, if such a character string is included in a Budget name, those characters are encoded as shown below.
Check out the help page below for more details.
For information regarding how to set up AWS integration, you can refer to the following help page (If using an existing IAM role, setting an additional
AWSBudgetsReadOnlyAccess policy is required).
For a while now, we’ve received a lot of interest in being able to use Mackerel to aggregate and monitor not only the statuses of various infrastructure resources, but also billing data such as this. This release is in response to those requests. Be sure to give it a try!
Support added for 1000+ registered queues in AWS / SQS Integration.
Up until now, only up to 1000 items could be integrated with AWS / SQS Integration, but with this update, that number is now unlimited.
This will probably only be relevant to a few special use cases, but if applicable to you, be sure to have a look.