Mackerel blog #mackerelio

The Official Blog of Mackerel

【Spec Change Notice】New metric targets for AWS・ALB Integration

Mackerel team CRE Inoue (id:a-know) here. Today’s announcement is centered around changes to specifications.

As the title states, newly obtainable metric targets are being added for AWS・ALB Integration. With these metrics, you’ll be able to monitor various percentile metrics related to the load balancer response, allowing for a more flexible response.

Specification changes

Load balancer metrics

  • Before spec changes

    • The following metrics were obtainable related to Target Response Time.
    • alb.response.time
  • After spec changes

    • The following metrics will be obtainable related to Target Response Time.
    • alb.response.time
    • alb.response.time_p90
    • alb.response.time_p95
    • alb.response.time_p99

Target group metrics

  • Before spec changes

    • The following metrics were obtainable related to Target Response Time per Target Group.
    • alb.response_per_group.TARGET_GROUP_NAME.time
  • After spec changes

    • The following metrics will be obtainable related to Target Response Time per Target Group.
    • alb.response_per_group.TARGET_GROUP_NAME.time
    • alb.response_per_group.TARGET_GROUP_NAME.time_p90
    • alb.response_per_group.TARGET_GROUP_NAME.time_p95
    • alb.response_per_group.TARGET_GROUP_NAME.time_p99

※ Enter the target group name in place of TARGET_GROUP_NAME.

Effects

With these specification changes, the maximum number of obtainable metrics will increase from 15 + 10 × (number of target groups) to 18 + 13 × (number of target groups). And even if there is only one target group, it will be converted into 2 micro hosts if the limit is exceeded (For more on the conversion of hosts when limits are exceeded, check out the FAQ・Handling of host conversion when plan limits are exceeded - Mackerel Docs).

Metrics obtained with AWS Integration can be freely selected in the configuration. Note that metrics will be retrieved by default and you can adjust as needed.

mackerel.io

Scheduled release date

The release that will include these specification changes is scheduled for Tuesday, April 14th, 2020 (JST).

This function was implemented at the request of Mackerel users. We greatly value your feedback (Feel free to contact our support team through the Mackerel Web console).

Azure App Service / Azure Functions now supported with Azure Integration

Hello. Mackerel team CRE Inoue (id:a-know) here. Today we have a big announcement!

Azure App Service / Azure Functions now supported with Azure Integration

f:id:mackerelio:20200313094531p:plain

Azure App Service is a PaaS provided by Microsoft Azure that allows you to easily build, deploy, and scale applications. I’m sure many of you who already use Microsoft Azure are familiar with the Azure App Service.

azure.microsoft.com

Azure Functions is an FaaS (Function as a Service) that implements serverless computing.

azure.microsoft.com

With this release from Mackerel, it’s now possible to integrate these services as Mackerel monitored hosts! Mackerel is strengthening its support for the integrated management and monitoring of various infrastructure-related resources. We hope you can put it to good use!

Check out the help page linked below for configuration methods.

mackerel.io

Also, be sure to check out the following help pages for the metrics obtainable with these newly added integrations.

mackerel.io

mackerel.io

The help page regarding IAM Policy for AWS Integration has been revised

A modification has been made to the IAM policy descriptions listed in the AWS Integration documentation due to incorrect permissions regarding S3.

mackerel.io

The original description s3: ListBucket has been changed to s3: ListAllMyBuckets.

OSS updates

Hello. Mackerel team CRE Inoue (id:a-know) here. This week’s release content comprises several OSS updates. Thank you to all those who contributed!

mackerel-agent

github.com

  • Specifying the following items in check monitoring items and metadata posting configurations has been made more intuitive
    • notification_interval
    • check_interval
    • execution_interval
    • The above items can be specified with a time such as 1h20m (1 hour 20 minutes). See Go’s Duration section for the notation.
      • If only an integer is specified, operation will continue the same as before
  • EC2 Instance Metadata Service v2 now supported
    • EC2 instances can be distinguished even in environments where only the EC2 instance metadata service v2 is valid

container-agent

github.com

  • EKS on Fargate now supported as a beta feature

mackerel-agent-plugins

github.com

  • [varnish] The following metrics have been added
    • backend_reuse
    • backend_recycle
    • Transient storage metrics

You can now select which metrics to retrieve with AWS Integration and more

Hello. Mackerel team CRE Inoue (id:a-know) here. So the cold weather has been relentless lately. Some days it feels like winter is never going to end.

Anyways, now on to the update announcements. We have a lot in store for you this week!

You can now select which metrics to retrieve with AWS Integration

f:id:mackerelio:20200205120407p:plain

Up until now, all of the metrics listed in the help page (= metrics that can be obtained with the Amazon CloudWatch API) were automatically linked with AWS integration. This didn’t require that you be aware of all these metrics, but you also couldn’t control the number of host metrics.

With this release, it is now possible to specify which metrics to integrate to Mackerel. If you have trouble controlling the host metric count, this is for you.

You can now specify the number of decimal places for numerical values displayed on widgets/custom dashboard

f:id:mackerelio:20200205120513p:plain

It is now possible to specify the number of decimal places for numerical values that are displayed on widgets available with custom dashboards. This can be particularly convenient for displaying the results of function based expressions in a numerical widget. We hope you can put it to good use!

IAM policies used with AWS Integration have been posted

A list of the IAM policies that are used with AWS Integration have been newly posted in the help page.

mackerel.io

Please use it as a reference when creating inline policies for integration targets.

New metrics available with Microsoft Azure・RedisCache Integration

The following metrics have been added.

  • Operations Per Second
  • Operations Per Second Shard

Operations Per Second Shard is only available with plans that support shards.

Official support for Windows Server now 2012 or later

This goes hand in hand with the end of support for Windows Server 2008 R2. Be sure to check out the updated help page as well.

mackerel.io

OSS Updates

go-check-plugins

  • [check-log] It is now possible to specify AND as a detection exclusion condition by specifying multiple --exclude

mackerel-agent

  • custom_identifier can now be configured when using Google Compute Engine instances

mackerel-client-ruby

  • Now supported for Faraday 1.0
    • Please note that updates can not be made with Faraday 0.x

Mackerel published in CNCF Landscape!

The CNCF (Cloud Native Computing Foundation) is an organization that compiles a list of companies and OSS projects that promote cloud native.

And Mackerel was recently featured in the CNCF's Cloud Native Interactive Landscape!

landscape.cncf.io

We look forward to bringing you even more of the benefits of cloud native technology through Mackerel.

A new event based on “The Feedback Whiteboard” from Mackerel DAY 2!

The feedback whiteboard was one of the most popular elements featured at last year’s Mackerel Day #2 event. For me, it was really cool to see so many participants actively exchanging opinions with the Mackerel staff in front of the whiteboard.

But, I also felt like we couldn’t touch on all of the input we received that day. For this reason, we are soliciting more feedback/requests from Mackerel users and holding a discussion event with the Mackerel staff! We’re calling it Mackerel Day #2 : More Whiteboard!

mackerelio.connpass.com (Japanese only)

This will be an event centered around your opinions and requests for Mackerel. Please join us!

Mackerel is now available as an event source for Amazon EventBridge

Hello. Mackerel CRE Inoue (id:a-know) here with the second blog article this week. And what's more, a surprise release announcement!

We are pleased to announce that Mackerel is now supported as an alert destination for Amazon EventBridge! In fact, the news was announced yesterday at the AWS Black Belt Online Seminar.

Mackerel is now available as an event source for Amazon EventBridge

Amazon EventBridge is a serverless event bus service provided by AWS.

aws.amazon.com

With EventBridge, building event-driven applications is easy because event ingestion and delivery, security, authorization, and error handling are all taken care of for you, and now Mackerel can be incorporated into that flow as well.

Be sure to check out the help page linked below.

mackerel.io

AWS Integration now supports AWS Batch and more

Hello! Mackerel team CRE Inoue (id:a-know) here.

It’s hard to believe we’re already almost a month into 2020 and this is the first release announcement of the new year. Happy new year everybody! Here’s to another great one.

Now on to this week’s releases.

AWS Integration now supports AWS Batch

f:id:mackerelio:20200117175541p:plain

With this release, Mackerel now supports the retrieval and monitoring of AWS Batch metrics. Information from multiple job queues in a region can be bundled and managed as a host. Billable targets are determined using the conversion 1 Region = 1 Micro Host. (Exceeding the maximum number of metrics per micro host may result in additional charges).

Be sure to check out the help page linked below.

mackerel.io

Alerts can now be filtered by time of occurrence

f:id:mackerelio:20200117175601p:plain

The filter function in the Alerts screen now allows you to filter through alerts based on the date and time of occurrence.

Here at Hatena, the Mackerel development team gets together two weeks and goes over the progress/changes in performance. If any of you Mackerel users out there have a similar situation where you’d like to review alerts from over a specific time period, this function can be super useful. By all means, give it a try.

The Check monitor introduction page has been revamped

Do you use check monitoring? Do you know what check monitoring is?

mackerel.io

As the help page above explains, check monitoring is an extremely useful function that can be used for not only detecting malfunctions, but also supporting automatic recovery and more. However, there is probably a decent number of people who are unaware of this function due to lack of documentation from the web console.

To combat this, we’ve revamped the Check monitor introduction page and made it so that you could reference the page from the Create a New Monitor screen.

The updated page covers everything from the very basics all the way up to advanced uses, so you’ll likely learn something new. Be sure to check it out! (Although please note that you can’t actually configure a new check monitor from this page….)

Mandatory 2-Step Authentication can now be enforced for organization access and more

Hello, Mackerel team CRE Inoue (id:a-know) here. I hope everyone had a good Christmas.

This year, just like every year, Mackerel held our own advent calendar for the holidays.

qiita.com (Japanese only)

I was privileged enough to take up the anchor position this year and published my article on the 25th! All of the articles were super helpful, and I enjoyed reading them every day. Thank you so much to everyone who participated!

Now on to this week’s new release information.

Mandatory 2-Step Authentication can now be enforced for organization access

It is now possible to require that 2-Step authentication be configured for accessing an organization. This can be done from the Organization’s Settings tab.

This can be a useful measure for improving security, so by all means, give it a try.

When creating a notification channel, you can now choose whether to add that channel to the Default notification group

In Mackerel, there are two general concepts surrounding notifications: 'Channels' and 'Groups'. A notification channel is setting information for sending notifications from Mackerel. Notification groups are bundles of one or more notification channels and are used to filter notification targets (e.g. ‘service A related notifications’ or ‘connectivity monitoring related notifications’ etc.).

One group in particular, the 'Default notification group', is special in that it acts as the basis for the organization. When a new notification channel was created, it was automatically added to this default notification group. The main purpose of this was to prevent notification oversights (e.g. forgetting to add a newly created channel to a notification group).

On the other hand, this contributed to unintended notifications. And preventing this problem by removing the channel from the Default group every time became somewhat of a hassle.

With this release, when creating a new channel, you can now specify whether or not you would like to add that channel to the Default notification group. This box is checked on by default, so if you haven’t had any trouble with this in the past, simply add the channel without unchecking the box and everything will be the same as before.

The release of alpha mackerel-container-agent for Amazon EKS on AWS Fargate

This was previously announced in a separate article, but here it is again!

mackerel.io (Japanese only)

As mentioned in the article above, the alpha version of mackerel-container-agent for Amazon EKS on AWS Fargate has been released and was announced at re:Invent, a recent AWS event.

This is the alpha version, so please give it a try if you are considering using EKS on Fargate.

Support window closed for the holidays from December 30, 2019 (Mon) to January 3, 2020 (Fri)

Mackerel's support window is usually open on business days, but will be closed from December 30th, 2019 (Monday) to January 3, 2020 (Friday) for the New Year holidays. Thank you for your understanding.