Welcome to 2018, in our journey to be the best monitoring platform, we’ve added a couple features to the cost reports and one for adding more scoping controls on the policies.
Not yet setup with Metricly? Start a free 21-day trial to see all the latest features in action!
Saved Emailed Reports
We have many reports that help you cross-analyze capacity resource utilization and AWS cost to help you optimize the performance and cost of your environment. We have just released an exciting new feature that lets you save these report settings so that you can easily switch between reports or share with colleagues. This data can be shared via the UI directly or by enabling our email notifications. Just toggle on email in the user interface to receive the custom report. A popular use case is to send it to an email alias so that the operations and development teams quickly discover the idle or over-sized EC2s before the bill gets large by the end of the month. Also the saved reports can include custom filters used to exclude EC2s by tag or name for example.
Modify Table Columns in Your EC2 Recommendations Report
Our users asked to customize our EC2 Recommendations report by removing or adding columns to it. The available options would be various attributes, tags or customized report functionality. The main use case is that when users receive a particular sizing recommendation they can see at a glance which region the EC2 belongs to or see the value of a given tag (ex. environment:staging). This new feature is particularly helpful since our support for emailed report was released, since users can decorate their reports with the added tags and attributes that are meaningful to them without having to log into our UI. We intend to add the same functionality to our other reports so keep an eye out.
Additional scope controls on policies
Our users asked for one additional filter for fine grain scoping of our alerting policies — and our engineers delivered this month. As you can see in the screen shot below, there are a number of existing filters available to help users narrow down the scope of an alerting policy such as Type (Linux server, EBS, ELB, JVM, etc.), Attribute (region, instanceType, etc.), Name Contains, and a few others. This new feature allows users to set a scope that includes a particular key:value pair tag (or multiple tags) while simultaneously excluding other tags. The increased control is to make sure that you only apply an alerting policy to exactly the computing resources that you care about and not receive any unrelated or false alerts. An example would be to scope an alert to cover resources associated with a particular micro-service, while excluding the development environment.