Mackerel Meetup was held yesterday.
To the many attendees who came and participated, thank you.
A detailed report entry is coming soon.
Here is this week’s update.
AWS Integration has been released
Currently, ELB and RDS are available.
Each AWS cloud product will be registered as one host in Mackerel and therefore be counted as a billable host. Additionally, the API of AWS will be called every 5 minutes for each targeted metric to be obtained. Please take note, for this reason, an Amazon CloudWatch API usage fee may occur.
In Mackerel, active hosts will be billed. Therefore, in order to remove a host registered in AWS integration from the billing target, delete the AWS Integration’s configuration. The host will become inactive and no longer a billable target.
Obtained metrics are treated the same as host metrics obtained by the agent and monitors can also be configured the same way.
For more information check out the help page.
This function is only offered in the Trial plan and Standard plan.
We have received a lot of feedback since the Wednesday press release and we will continue to promote the improvement of this function. By all means, please let us know your opinions and impressions.
Release of mackerel-agent etc.
mackerel-agent, mackerel-agent-plugins, and mkr have been released.
With this update, the version of Go used for the build, will become version 1.6.2
The specific updated contents for each are as follows.
- mackerel-agent’s path to /usr/bin
- retry when the retiring process fails
- output the plugin run-time error to the log
- stability improvement
- mackerel-plugin-docker: parallelizing acquisitions from the metrics API
- addition of
isMuteto monitor settings items