Mackerel blog #mackerelio

The Official Blog of Mackerel

It’s now possible to leave an organization etc.

It’s August! And like we announced last week, Hatena has entered a new term. On July 31st, a company-wide meeting was held and all members of the Mackerel team got together.

We also added some new members to the team! Get ready for even more development!

Anyways, here is this week’s update information.

It’s now possible to leave an organization

Up until now, in order to leave an organization that you belong to, action from a user with administrator authority was necessary. Now we’ve made it possible to do this on your own.

This operation can be performed from the account screen’s organization tab.

Updates for Mackerel-agent-plugins and cookbook-mackerel-agent

mackerel-agent-plugins has been updated to v0.29.1, and cookbook-mackerel-agent has been updated to v1.3.0.

mackerel-agent-plugins

  • [accesslog] Log format detection logic improved
  • [solr] graph definitions improved

cookbook-mackerel-agent

  • Enabled to specify environment variable
  • Other minor modifications made to README etc.

A big thanks to everyone who contributed to the above repository!

First stage of large-scale maintenance starts Monday of next week (8/7)

We’ve talked about the large-scale maintenance scheduled for August in previous blog announcements, and now the time has come. The first stage of maintenance starts next Monday, August 7th.

Below are the entries with detailed information regarding the maintenance. Be sure to take another look.

mackerel.io

mackerel.io

Mackerel UG Meeting vol.3 scheduled for 8/23 (Wed.)

The Mackerel User Group was put together by a group of Mackerel user volunteers. This will be the group’s third event, to be held on Wednesday, August 23rd.

mackerel-ug.connpass.com

The theme for this event is XaaS meets Mackerel so it should be a good opportunity to hear about interesting and useful manners of application! A few of the Mackerel team staff are planning to stop by as well. I hope you can join us!

Notice for Obon holiday【8/11(Fri.)- 8/16(Wed.)】

The Mackerel team will be out of the office from August 11th (Friday) until August 16th (Wednesday) for the Obon national holiday. During this period, we will be taking a break from our weekly update blog and the support window (except for emergencies).

Our next update blog entry will be on Friday, August 18th. Have a great summer vacation everyone!

Notification failure from Mackerel to OpsGenie accounts created after May 30th, 2017

Thank you for choosing Mackerel.

Currently, there is an issue with notifications failing from Mackerel to OpsGenie depending on certain conditions.

Notification failures occur when a notification from Mackerel is sent to an OpsGenie account that was created after May 30th, 2017. Notifications sent to accounts created before said date have been successful.

The cause of these failures is due to OpsGenie’s REST API switch to V2.

Mackerel uses OpsGenie’s REST API V1 for integration with OpsGenie. V1 and V2 are not compatible, and the use of V1 has been closed for accounts created after May 30th, 2017, which is why notifications from Mackerel are failing.

Mackerel is working on transitioning to the use of API V2, however, specification changes and support analysis will take some time.

Below is the announcement from OpsGenie about their API switch. www.opsgenie.com

We apologize for the inconvenience.

Another announcement will be made when the issue has been resolved.

Notification of further maintenance scheduled for late August (Aug 21st)

Hi, Mackerel sub-producer id:Songmu here. As mentioned in a [previous post] (https://mackerel.io/blog/entry/announcement/20170711), we will be carrying out maintenance on August 7th (Mon), followed by a second stage of maintenance. The date for the second stage of maintenance has now been set, so I will let you know the details below.

Date and time of second stage of maintenance

Monday, August 21st, 2017 from 2:30pm to 3:30pm (JST)

Details of work

Relocation of the URL external monitoring, AWS integration, and Azure integration subsystems.

Range of impact

Service will not be suspended. However, there is a possibility that monitoring via the affected subsystems mentioned above may become unavailable several times whilst the work is carried out.

After the maintenance is complete, the source IP address used for Mackerel notification channels, such as URL external monitoring, AWS integration, Azure integration and Webhook, will change. Email notifications will remain unchanged.

Furthermore, in the case of URL external monitoring, the monitoring conditions including location will be updated, so the trend of measured response times may fluctuate slightly.

The list of affected and new IP addresses can be found in a previous blog entry, so please also check this post in conjunction.

mackerel.io

About announcements on the day

We will make announcements on the status page (http://status.mackerel.io).

Status updates will appear on the status page as necessary. In the unlikely event that the maintenance period is extended, we will also inform you of this via the status page.

Furthermore, after the maintenance has been completed, we will post details on this blog, including the actual time taken.

If you have any queries regarding this matter, please contact us via email, at support@mackerel.io.

Thank you for your support of Mackerel, we look forward to continuing to work with you in the future.

Updates for mackerel-agent and more etc.

Hello. Mackerel sales engineer Inoue (id:a-know) here.

Hatena inc. will come to the end of the term this month and enter a new one starting in August. In preparation for the new term, the Mackerel team is thinking about all kinds of new projects and events.

We’ve been discussing a lot of new events focused on user interaction in particular. Our Hackathon event, which we’ll introduce later in this blog, will be the first installation. You definitely don’t want to miss out on Mackerel next term!

Anyways, here is this week’s update information.

Updates for mackerel-agent and more

Updates have been made for OSS mackerel-agent, mackerel-agent-plugins, and go-check-plugins. Below is an outline of the update contents.

mackerel-agent v0.44.0

  • Minor adjustments

mackerel-agent-plugins v0.29.0

  • [aws-dynamodb] TimeToLiveDeletedItemCount metrics now obtainable.
  • [aws-dynamodb] option and graph definition have been adjusted.
  • [mysql] label prefix improved.

go-check-plugins v0.11.0

  • [check-http] -i option added.
    • The source IP address can now be specified.
  • [check-http] -s option added.
    • By using this option and setting -s 404=ok and -s 300-404=critical , it is now possible to associate the status code with the check results.

Notice for Maintenance in the end of August・Concerning stage 2

Here are the details concerning the second round of scheduled maintenance in the end of August.

mackerel.io

After this maintenance is completed, source IP addresses used for notification channels such as URL external monitoring, AWS Integration, Azure Integration, Webhook from Mackerel will be changed.

The IP addresses are listed in the first announcement entry we made concerning this maintenance.

mackerel.io

If you are specifying an IP address for the purpose of allowing access only from Mackerel, be sure to check it again.

Mackerel Plugin Hackathon #1!

I briefly mentioned this at the beginning, but starting next month we would like to hold a variety of events more than ever before. And first up is Mackerel’s very first hackathon event, Mackerel Plugin Hackathon #1!

mackerelio.connpass.com

For the event venue, we were able to rent the lovely space of VOYAGE GROUP!

id:Songmu , id:Soudai , and me (id:a-know) from the Mackerel team will be attending the event and providing support for anyone not familiar with creating Mackerel plugins, so don’t worry!

Have you ever thought, “This plugin doesn’t exist, so I’ll make it myself!”? Then this event is for you! We also warmly welcome anyone who might be interested in deepening their understanding of plugins/Mackerel and those wanting to interact with Mackerel engineers/users.

If you have the time, feel free to join us!

Details regarding the maintenance scheduled for August 7.

Mackerel Sub-producer id:Songmu here. This announcement is regarding the details of the early August maintenance announced previously.

Maintenance Date and Time: August 7, 2017 From 2:30 p.m. to 4:30 p.m. (JST)

The switchover will be implemented while the system is online, but as a result of this the following circumstances will occur one or two times to the Mackerel main system during the time frame listed above.

  • Unresponsiveness for less than 10 minutes.
  • After the above, a period of about 20 minutes of instability.

The following will occur during the period of unresponsiveness.

  • API access stoppage.
    • Across-the-board failure of agent or mkr requests.
  • Web screen access will also fail.
  • Connectivity Monitoring alert stoppage.
  • Subsystem stoppage (external monitoring, AWS integration, Azure integration).

The following will occur during the period of instability.

  • Reduced response performance .
  • Higher probability for access failures.

Effects of access failures.

In regard to the metrics posted by mackerel-agent or fluentd, these are buffered within the process itself and are later retransmitted, resulting in no data loss occurring. It is possible that there may be some loss related to metrics posted by independent systems such as cron.

In some cases, temporary issues have been observed in the graph data immediately after the system becomes responsive once more. However, the graph will display normally once the mackerel-agent buffer has finished retransmitting data.

During the time frame listed above, alerts will not send false alarms, but there is a possibility that the sending of alerts will not operate normally.

Regarding metric monitoring alerts, Mackerel’s system makes decisions on alerts when the metrics are received, so no false alarms will occur during the time frame listed above.

However, because mackerel-agent buffer retransmits in the order data was posted, it is possible alerts will not be sent in the case of certain settings, such when monitoring average values. In addition, in the case of check monitoring, alerts will not be sent when the API request fails.

About the announcement on that day

We will make an announcement before and after maintenance via the newsletter and the status page (http://status.mackerel.io).

Updates of the situation will be posted on the status page when necessary. In the unlikely event of the time frame for maintenance being extended, we will inform you via the status page.

In addition, after maintenance has been completed, we will post details on our blog, including the actual downtime.

Purpose of the Maintenance

There will not necessarily be new functionality added after a release, and this maintenance is in anticipation of scalability improvements, performance upgrades to the time series database, and functionality enhancement. In particular, there are plans to make changes to the time series database to allow for long-term archival of data with one-minute granularity.

For any inquiries regarding this matter, please contact us via email at support@mackerel.io.

We thank you for your support of Mackerel and look forward to continuing to work with you in the future.

Updated agent installation process page, etc.

Hello! Mackerel sales engineer Inoue here.

This Wednesday, we held the Mackerel Drink Up #5 Tokyo event. Being visited at our Hatena office in Tokyo by those who have been using Mackerel on a daily basis, and enjoying delicious food while discussing Mackerel stirred up quite the sensation!

Halfway through we began lightning talks (LT), which had the venue wrapped in laughter from beginning to end.

We had great success in holding Drink Up #5, and plan to hold various other events in the future. If there is anything you might like to attend, by all means do come along.

Anyway, here is this week’s update information.

Updated agent installation process page

If you are a Mackerel user, you will likely have seen the Mackerel agent installation process page before. With this week’s update, this page has become even more intuitive and easier to use.

Some of Mackerel’s special features are its incredibly easy installation process, and the speed in which monitoring can begin; we highly recommend Mackerel to those who may not have had any experience with server monitoring before. Further, if there is anything you feel that we can do to make the startup procedure even easier, please do not hesitate to leave feedback!

Settings to combine stacked and line graphs can now be found within UI settings

It is now possible to change the settings within the UI for Mackerel’s metric graphs, so as to display both the “stacked graph,” which displays the value of each metric stacked one on top of the other, and the “line graph,” which displays data as overlapping line segments, on top of one another.

https://cdn-ak.f.st-hatena.com/images/fotolife/m/mackerelio/20170721/20170721085926.png

https://cdn-ak.f.st-hatena.com/images/fotolife/m/mackerelio/20170721/20170721131029.png

These settings can be accessed by either displaying “Graph Definitions” by clicking on the gear icon in the upper right-hand corner of the graph, or through the Graph Definition Edit Screen (this can also be set with service metric graphs). Please try it out!

Azure Integration now supports Redis Cache etc.

Hello! Mackerel sales engineer Inoue (id:a-know) here.

The other day we made an announcement on this blog about maintenance scheduled for early August.

mackerel.io

Unlike normal maintenance, this is in preparation for Mackerel’s growth further down the road. We will put forth maximum effort in order to keep the maintenance’s impact to a minimum, but users may still be affected so we’re letting you know in advance. Please take a moment to read the entry above.

Anyways, here is this week’s update information.

Azure Integration now supports Redis Cache

We’ve already expanded support for Azure Integration which was just released at the end of last month. Following SQL database, this time we’ve expanded support for Redis Cache.

azure.microsoft.com

Right now I think it’s fairly popular to configure a caching mechanism using Redis as part of the system. Even if Redis cache is configured by Azure, it’s possible to collect those metrics in Mackerel. By all means, give it a try.

Now accepting applications for Mackerel Drink Up #5 Tokyo! First-come-first-served!

Last week we announced the event Mackerel Drink Up #5 Tokyo, and now we’ve slightly increased the limit of participation! There are still a few spots left and applicants will be selected on a first-come-first-served basis!

mackerelio.connpass.com

This is your chance to talk to people behind Mackerel , so be sure to apply!