Mackerel blog #mackerelio

The Official Blog of Mackerel

A feature to obtain closed alerts added to the alert list API and more

Hello! Mackerel team CRE Miura (id:missasan) here.

Now into December, advent calendars have started all over the place. Various campaigns and sales wars that are custom during this time of the year are also happening. And depending on your operational service, this may have an effect on your system or server status. Since Mackerel retains metrics with a 460 day 1 minute granularity, how about consolidating your key graphs into a new custom dashboard and looking over last year's access and resource statuses with your team members?

mackerel.io

Now on to this week’s update information.

Communication via TLS 1.1 will stop on Tuesday, January 8th, 2019

As announced in the article linked below, correspondence via TLS 1.1 will stopped on Tuesday, January 8th, 2019. For more details, see the following.

mackerel.io

A feature to obtain closed alerts added to the alert list API

Closed alerts can now be obtained by specifying withClosed in the query parameters. For details, check out the help page linked below.

mackerel.io

Along with this, we’ve restricted the maximum number of alerts that can be obtained at once with the API to 100 cases. To obtain more than 100 alerts, specify nextId and retrieve alerts previous to the specified alert id.

RequestCountPerTarget added to AWS Integration ALB

As requested by users, we added a metric that counts the number of requests for each ALB target group. For more details, refer to the help page linked below.

mackerel.io

Communication via TLS 1.1 will stop on January 8th, 2019 (Tue.)

Thank you for choosing Mackerel.

As stated in the title, on Tuesday, January 8th, 2019, encrypted communication via TLS 1.1 will be stopped.

Impact range

Browsing mackerel.io will no longer be available from older OSs and browsers that do not support TLS 1.2 or later.

We recommend using our services in officially supported environments*1 applied with the latest patches etc. If TLS 1.2 or later is not yet supported, please transition to a supported environment.

We apologize for any inconvenience and we appreciate your understanding of the importance of providing our services in a secure environment.

Thank you for choosing Mackerel.

AWS Integration now supported with Kinesis Data Streams and more

Hello! Mackerel team CRE Miura (id:missasan) here.

Only a few days left in November. How the time flies. The end of the year is finally upon us. Do you already have plans for this holiday season? Mackerel Drink Up will be held on December 11th (Tuesday). As we still have openings for the LT, if you or someone you know has some material to announce before the New Year, why not do so at Mackerel Drink Up?

Now on to this week’s update information.

【Advance release notice】Incompatible specification changes for the alert acquisition API

With the release on November 29th, 2018 (Thursday), a feature will be added to obtain closed alerts with the API, along with changes made to specifications incompatible with the alert acquisition API. Please see the blog post below for more details regarding the content of the changes etc.

mackerel.io

AWS Integration now supported with Kinesis Data Streams

For detail regarding obtainable metrics, refer to the help page below.

mackerel.io

Host memos can now be included in text alert emails

Host memos can now be included in text alert email. (also previously included in HTML mail) You can add memos from the host detail screen (https://mackerel.io/my/hosts/【hostId】) shown in the image below. Put this feature to good use by writing down things to watch out for or handy details that can help during troubleshooting, etc.

The problem of not being able to obtain disk metrics is now fixed with Linux kernel version 4.19 or later in mackerel-agent v 0.58.2

Update mackerel-agent to the latest version and give it a try.

--connect-to option added to check-http

The --connect-to option added with this update is useful if you’d like to monitor whether the response being made when directly responding HTTPS with an HTTP application server or TLS terminal reverse proxy is being made with the correct certificate corresponding to the specified domain. Refer to the following link for usage options.

github.com

Improvements made to mkr command in preparation for the release of API to obtain closed alerts

We’ve made some upgrades in order to be compatible with the scheduled release of the closed alert acquisition API as mentioned in the 【Advance release announcement】 above. If you’re running the alert API with mkr command, please consider updating with the latest release. The feature to obtain closed alerts (--with-closed option) will be available after the API feature release.

Mackerel Drink Up #8 Tokyo!

Mackerel Drink Up will be held at Hatena's Tokyo office. And although we’ve already received quite a lot of applications, LT slots are still available. Come join us.

mackerelio.connpass.com (Japanese only)

Event details

  • Date and time:December 11, 2018 (Tue) 7:00 pm ~ 9:00 pm (Reception starts at 6:45 pm)
  • Location:Hatena Tokyo office(3rd floor, Seminar room)[MAP]
  • Capacity:15 people, LT - 3 people
  • Cost:Free

Our support window will be closed for the holidays

Both ways of contacting our support team, either through support@mackerel.io or with the “contact our support team” option displayed in the upper right header when logged into Mackerel, will be closed during the following dates for the New Year’s holidays.

New Year’s holiday period :Tuesday, December 25th, 2018 - Thursday, January 3rd, 2019

All inquiries received during this period will be handled sequentially starting after the holidays.

【Advanced release notice】Added feature to obtain closed alerts, along with changes to incompatible specifications for the alert acquisition API

Mackerel Director id:daiksy here.

This week, we will be adding a feature to obtain closed alerts to the alert acquisition API. This feature was highly requested. Along with this new feature, we will be making changes to specifications incompatible with the alert acquisition API.

mackerel.io

The extent of impact caused by the specification changes is as follows.

  • Users who currently obtain an open alert list via API
    • Alerts will not be obtainable if more than 101 alerts are open at the same time.
    • If you use mkr to get an alert list and update in advance, there will be no effect due to the fact that mkr 0.34.2 and later will be cared for internally.

The release date and contents of the specification changes are as follows.

  • Release date: November 29, 2018 (Thursday)
  • Release content: Addition of withClosed limit nextId parameter to the alert acquisition API to get closed alerts
  • Change content: The default limit is 100, so if the limit is not set, the maximum number of retrievals will be 100. This also applies to obtaining open alerts in regards to similar requests before specification changes.

Since the number of closed alerts is cumulative, this number can grow to be enormous for organizations that have been operating for a long time. Therefore, it has became necessary to add some sort of paging process for obtaining closed alerts. Because adding this process will affect the behavior of the existing API, we’ve will notify you in advance regarding these specification changes.

Regarding mkr and mackerel-client-go

Regarding mkr, please be aware that if you’re using mkr 0.33.0 or a previous version after November 29th, you will only be able to obtain up to 100 alerts. As versions of mkr and mackerel-client-go that support the new API have already been provided, please update as necessary.

Thank you for choosing Mackerel.

The newly renovated Custom Dashboards and more

Hello! Mackerel team CRE Miura (id:missasan) here.

Last week we announced the Mackerel Advent Calendar, but this year, Inoue (id:a-know) and I are trying our hands at a CRE team specific calendar as well, the Mackerel Advent Calendar 2018 (CRE)!

Now, not only do you have Mackerel Advent Calendar to look forward to, but our calendar as well!

qiita.com (Japanese only)

Now on to this week’s update information.

The newly renovated Custom Dashboards

Custom Dashboards is a dashboard feature that lets you freely arrange graphs that you want to see based on usage scenes etc.

With this update, Custom Dashboards has been newly reborn. Now it’s even easier to create and edit dashboards with more flexibility, add graphs by dragging and dropping, change display sizes and positioning, and more.

3 types of widgets

The types of addable information (widgets) are increasing.

Graph widgets

Various graphs can be displayed. Expression graphs can also be created and added from here.

Value widgets

Display the latest values of various metrics in numbers. You can also select expressions for metric type.

Markdown widgets

As with previous Custom Dashboards feature, you can freely write content in Markdown format.

Use it in various scenes

Dashboards can be created easily and put to good use in various scenes of server monitoring and operation!

  • Daily service status checks
  • Reference at weekly/monthly team meetings
  • Use in capacity planning
  • Look back on the system’s status and effects when the campaign was implemented

Automatic registration using the API

Even with the new Custom Dashboards, it’s possible to import and export graphs using the API. This lets you automate the creating / editing of custom dashboards.

For more details, check out the following document.

mackerel.io

Please note that operations using the mkr command for the new Custom Dashboards are not yet supported.

The old Custom Dashboards

With this change, the old Custom Dashboards has been renamed "Legacy Custom Dashboards". You can also browse previously created dashboards here.

We recommend that you use the new Custom Dashboards feature when creating a new dashboard.

check-redis subcommand replication added

replication has been added to the subcommands of check-redis. This makes it possible to check whether Redis replication is working properly. slave is a similar subcommand, but understand that it will become obsolete in the future.

Organization names can now be obtained with mkr org command

The organization name can now be obtained by running mkr org. The following execution results are obtained.

{
  "name": <name>
}

A practical DevOps Hands-on Workshop 〜 Building a safe/secure DevOps environment with AWS and Mackerel!

This is an event announcement.

This event is a hands-on workshop for beginners to Mackerel and the AWS Code series. If you’d like some practical experience with DevOps environments that combine monitoring and CI/CD pipelines, please come and join us!

Mackerel team CRE Inoue (id:a-know)will be presenting at the event!

dev.classmethod.jp (Japanese only)

Event details

  • Date and time:December 10, 2018 (Monday) 2:00 - 4:30 p.m. (Reception start: 1:30 p.m.)
  • Location:Shibuya Hikarie 11th Floor Sky Lobby Conference Room D [MAP]
  • Capacity:24 people
  • Cost:Free
  • Co-sponsors:Classmethod Inc., Hatena Co., Ltd

API Gateway now supported with AWS Integration and more

Hello! Mackerel team CRE Miura (id:missasan) here.

November has finally come and winter is steadily approaching. And with this time of the year, comes the advent calendar season. I’m sure that everyone is watching and waiting to decide which events to participate in this year. Even here at Mackerel, our annual advent calendar is in the works.

qiita.com

Here are a few of Mackerel’s advent calendars from past years.

The advent calendar was originally a calendar used to count down the number of days until Christmas, looking forward to and enjoying each day by opening up little windows to find small candies or chocolates. I’m excited about the fact that is year’s Mackerel advent calendar will be one that gives nice little gifts to all our users.

If you’ve tried out Mackerel for a year, we'd love to hear what made you happy or some things you struggled with. If you’ve never made an advent calendar before, why not make your debut with Mackerel? By all means!

Now on to this week’s update information.

API Gateway now supported with AWS Integration

Following CloudFront, is support for API Gateway. Refer to the following link for details regarding obtainable metrics.

mackerel.io

AWS Integration features are being released one after another. If you haven’t changed your integration settings in a while, be sure to take a look at this in review.

ALB now supported with mackerel-plugin-aws-waf

Up until now, only AWS WAF metrics deployed to CloudFront were targets with mackerel-plugin-aws-waf, but with this update it’s now possible to obtain ALB targeted metrics as well.

github.com

This is a feature made possible by user contributions. Thank you very much!

A posting limit has been set for API service metric posting

Mackerel’s time series data has a granularity of 1 minute, and any metrics posted at a higher frequency than that are overwritten. With this update, we’ve set a limit on the number of service metric postings by API.

If the limited number of posts for each endpoint is exceeded, status 429 is returned. Be careful not to set a posting frequency below once per minute.

In addition, it’s also possible for the service metric posting API to send multiple metrics at once. By sending multiple metrics together instead of one by one, you can avoid posting restrictions on the API. For more details, refer to the help page.

Monitoring solution seminar featuring: Cloud Portal x SIOS Coati x and Mackerel!

Sony Network Communications (Cloud Portal), SIOS Technology (SIOS Coati), and your very own Hatena (Mackerel) are holding a seminar together.

Event outline

  • Date and time: Wednesday, December 12th, 15:00-17:30
  • Location: Akihabara UDX 4F Next-2 (2 min walk from Akihabara Station)
  • Capacity: 80 people

Sign up here

www.bit-drive.ne.jp (Japanese only)

A new feature has been added to display maintenance and incident information from the management screen etc.

Hello! Mackerel team CRE Miura (id:missasan) here.

We recently released a new case study featuring SEGA Games and their use of Mackerel in social network gaming environments. This article goes over the introduction of Mackerel motivated by transitioning to the cloud and how it’s used in daily operation. Be sure to check it out!

Now on to this week’s update information.

A new feature has been added to display maintenance and incident information from the management screen

When Mackerel is under maintenance or if an incident has occurred, a message will now be displayed at the top of the screen as shown in the below images.

During maintenance

During an incident

Now it’s possible to see information from Mackerel’s status page in a more convenient way. Use this to eliminate false alarms. For more detailed information, continue to check the status page and follow our official Twitter timeline.

A plugin name can now be set to User-Agent for plugins that send http requests

For plugins that send http requests, a plugin name such as mackerel-plugin-plack can now be set to the User-Agent at the time of request. Up until now, the standard User-Agent of Go was used.

Now, we can easily distinguish where the request was issued with User-Agent when viewing the access log. Please be cautious when using User-Agent for access restrictions etc.

SEGA Games case study!

Check out our latest case study through the link below!

mackerel.io (Japanese only)