Hello. My name is Igarashi (id:masarasi) and I'm from Mackerel Team CRE. I'm going to fill you in on the details of this update.
- Role assignment feature using AWS tags released
- Cookies are supported at redirect by external monitoring
- Problems with mackerel-container-agent have been resolved
Role assignment feature using AWS tags released
The following nine services are supported by this release.
Please check the following link for help on how to use AWS integration.
Additionally, some common questions about this new feature are addressed below. If you have any other questions not covered here, please contact our support team.
We would also very much appreciate you providing us feedback including opinions and requests.
operations when set simultaneously with the default role
mackerel-integration tag content takes priority, meaning that no default role is set (already assigned service roles remain). If you also want to assign the default role, please use the aforementioned multiple role setting.
different uses with the default role
Within the service role settings of the mackerel-integration tag, because AWS resources and the service roles that you want to associate with them are set as tags for AWS resources, you will be able to manage service roles on a per AWS resource basis. As for setting by tag, we essentially recommend using this method as it makes it possible to create more detailed settings such as assigning multiple service roles to one single AWS service. The default role is most suitable for AWS services not requiring separate service roles.
When tagging an existing host
Keep the tags that have already been set up and add the tags set in the mackerel-integration tag.
Even if the tags are set, the service roles for the host are not reflected
Because roles are assigned at regular intervals to each host, so it may take some time to see these roles reflected. If they do not come into effect after several hours, check to ensure that the Mackerel service role contains no unusable letters.
Furthermore, for hosts that have run mackerel-agent even one time previously, host information registered via mackerel-agent is given priority, so even if the mackerel-integration tag has been set, it will not be updated.
As for Amazon Aurora, you can set tags for both cluster and instance, but this particular feature refers to the cluster tag. Aurora Serverless also refers to the cluster tag.
Cookies are supported at redirect by external monitoring
When the "Redirect according to response header" option is enabled in external monitoring, cookies issued by monitored URLs are then preserved in the redirect destination. Please note that due to changes in this feature, some of the ways that external monitoring operates may have been altered.
Specifications of URL external monitoring are also described in the link below, so please take this chance to review this helpful information.
Problems with mackerel-container-agent have been resolved
The following problems with mackerel-container-agent have been resolved
- Resolved the problem of metrics being interrupted when the setting is automatically reloaded when the mackerel-container-agent settings were loaded from Amazon S3.
- Resolved the problem when mackerel-container-agent would fail to start when it was used on Amazon EKS, IRSA (IAM Roles for Service Accounts) was enabled, and the settings were loaded from Amazon S3.
Mackerel will continue updating container-related features, so if you haven't got around to using it yet, please do give it a try to discover its advantages!
Please follow the link below to read more on how to use mackerel-container-agent. We look forward to receiving your feedback including opinions and requests!