CloudWatch Importing



Just wanted to let everyone know about a quick update to the CloudWatch integration.

Several users have had troubles knowing the correct permissions needed on their IAM credentials, and it is totally our fault because the integration is very opaque about what it is doing.

Previously, if there was an error, it would just silently fail and no metrics would be imported. Now, if there's any kind of permissions error, we'll show a message on the credentials form about what needs to be done to resolve the issue. After you fix the permissions, "save" the form (even if none of the values changed), and the importer will try again.

For more details about what permissions are needed, check out our knowledge base article, and feel free to email support or drop by our support chatroom with any questions.

Introducing Librato AWS CloudWatch (Beta)



At the AWS Summit in San Francisco today, we’re introducing Librato for AWS, a turn-key solution for Amazon CloudWatch users who are looking for ways to get more out of the data CloudWatch is collecting for them.

The Beta version is available for AWS customers hosting applications in US-East and provides pre-configured instruments and dashboards for all of your EC2 metrics, with support for additional AWS regions and services under way.

Librato for AWS Benefits.

These are some of the benefits you’ll enjoy as compared to CloudWatch when using Librato for AWS:

  • One year data retention: We keep your data for a year, allowing you to do trend analysis, capacity planning and comparative analysis.
  • Persistent correlations: You can build instruments that show a number of metrics from multiple sources together. Instruments persist, so you have them available any time you need. This is a great tool for fire-fighting or just building a grouped set of metrics and saving them as an instrument that you can then display on a dashboard.
  • Configurable and shareable dashboards: You can build dashboards that combine instruments that you like to view together, for example showing all metrics for a server instance, a cluster, a database, or an application. Build as many as you want and easily share read-only versions with others.
  • Live update of instruments and dashboards: Instruments and dashboards are refreshed in real time, so you can easily monitor the health of your AWS resources on any display, from tablet to wall-mounted monitor.
  • Instrument and dashboard templates: If you’re provisioning large numbers of identical resources, such as server instances, there’s no need to build instruments and dashboards for each of them. You can build a curated set of instrument and dashboard templates for each set of resources of a specific type and dynamically instantiate one for a specific resource any time you need it.
  • Annotations: In addition to data streams you can send us annotation streams for aperiodic events, such as software deploys or configuration changes, that you want to correlate with metrics you are tracking. You can visualize annotations in the instruments of your choice.
  • Integration with popular collaboration tools: You can post snapshots of instruments in chat rooms like Campfire and Hipchat and send alerts to service integration tools like PagerDuty and OpsGenie.
  • Custom metrics with resolution up to 5 sec.: You can add custom metrics through one of our language bindings or one of the many open source monitoring tools can send data to Librato.

Pricing

Our new standard pricing applies for data we collect from CloudWatch. This means that for 5 min. resolution data streams (the default resolution CloudWatch uses) you will be charged $0.05/mo. and for 1 min. resolution streams (used for detailed monitoring of EC2 instances) $0.10/mo.

Different from CloudWatch, we do not charge for Alerts or API calls and you can add as many custom metrics as you like, from $0.05/mo for 5 min. resolution to $0.30/mo for 5 sec. resolution data streams. This means that if you’re an extensive user of Alerts and Custom Metrics, you may even save money by using Librato for AWS!

How to get started

You can read the step by step instructions in the "Using Librato with Amazon CloudWatch" knowledge base article but in essence it's as simple as logging in to your Librato account (if you don't have one you can sign up for free), adding your read-only AWS credentials and picking a region and a service.

For this beta release we only support US-East and EC2 but we will add support for additional AWS regions and services in the near future.

That’s all that’s needed to start seeing your CloudWatch metrics in the instruments and dashboards we’ve curated for each service and use all of the features our service provides for getting the most out of the data CloudWatch collects.

Let us know which regions / services you want us to integrate first by answering two questions in this survey: http://surveymonkey.com/s/librato_cloudwatch.

Introducing: Stream Based Pricing



Today we’re introducing a new pricing model that reflects what we’ve learned about the many ways in which our customers use our service, and the good feedback we’ve received on our current “per measurement” pricing model since we launched our service. Before delving in the details, here’s a summary of the changes:

  • We’re now charging “per data stream” instead of “per measurement”. This gives us more flexibility to price for value, for example based on resolution and retention. We use this flexibility to reduce costs for high resolution data streams and charge a fairer (higher) price for low resolution data streams.
  • We now have a free “Developer” plan that includes 100 data streams that are limited in resolution and retention. Users of the Developer plan have access to our knowledge base, and “best effort” chat and email support.
  • For unlimited use of our service and priority access to email and live chat support you can use our pay-per-use “Production” plan. There is a minimum charge of $5/mo. for this plan.

If you currently have a paid or trial account you will be able to choose between continuing on the old or the new pricing model. For new users the new pricing is effective immediately.

Why are we changing our pricing?

These are some of the things we’ve learned since we launched our service, that are reflected in our new pricing model:

  • Some find us too expensive for use cases that require high resolution data streams (sampling intervals of 30 sec. or less).
  • When used for low resolution data streams, such as business metrics, our pricing does not reflect the value we provide. Quite a few customers have told us that we do not charge them enough for the benefits they get from our service.
  • Some customers use less than $1 in services per month. As the number of users of our service grows, we need to make sure that we can continue to provide great support and reflect the value of this in our pricing..
  • Though most customers seem to like pay-per-use pricing, some are concerned about inadvertent high charges and a few have expressed interest in subscription pricing.
  • Some find the per measurement pricing non-intuitive and/or confusing.

How does the new pricing work?

We charge per data stream, based on its resolution.

A data stream is defined by a metric and a source, for example, the metric could be CPU load and the source a specific server instance. At this time we support resolutions up to 5 sec.

We offer a 30 day unlimited free trial during which you have unrestricted use of our service. After the trial period you can sign up for the Production plan or continue with the more limited Developer plan.

Per data stream charges increase with resolution. For example, we charge $0.30/mo. for a data stream with 5 sec. resolution, and $0.05/mo for a data stream with 5 min. resolution. As compared to our current pricing, data streams with 5-30 sec. resolution will be less expensive (e.g. a 5 sec. resolution data stream will cost less than 30% of what it costs today), 60 sec. resolution data streams will cost about the same, and data streams with >60 sec. resolution will be more expensive.

Developer plan.

The Developer plan allows you to send us up to 100 data streams with a maximum resolution of 60 sec. and a 1 day retention period, or a maximum resolution of 5 min. and a 2 week retention period. The plan includes 10 alerts, 2 annotation streams, one dashboard, access to our Knowledge Base and “best effort” email and chat room support.

Production plan.

The Production plan has a minimum charge of $5/mo, for which you get unlimited access to our service, and priority access to email, and live chat support.

For convenience we list our prices “per data stream, per month”, but we charge you per data stream per hour (we assume you’re not really interested in knowing that a 60 sec. resolution data stream will cost you about $0.000139 per hour).

Only pay for the data we keep.

Librato now offers “service side aggregation”. You can use this to combine multiple streams into a single stream, for example to combine streams originating from multiple processes into a single application level stream. If you’re sampling data at a higher resolution than you want to keep it, you can also use this to let us aggregate data points and store the stream at lower resolution. The good thing is that we only charge you for the aggregated data streams we store for you.

Pay as you go.

By default, we’ll continue to charge your credit card for your use of our service at the end of each service month (see comments on subscription pricing below).

Volume discounts.

We offer volume discounts for customers consuming more than $400/mo in services.

Optional “cap”.

In the near future we will allow you to set a “not to exceed” amount for your monthly charges and alert you if you’re on a path to exceeding your monthly cap. Until the monthly cap is supported in our service, you can contact us to set a cap if this is important for you.

If you exceed the cap, we will continue to accept your data, but you will not have access to the data until you increase the cap, or the start of the next service month. We will not delete or stop accepting your data because you exceed your cap.

Optional monthly subscription.

A few customers have expressed interest in a subscription with fixed monthly payments. Although we’re not making this generally available at this time, we have devised a “define your own subscription” scheme, which we will make available to customers on request.

Where can I find more details?

You can find a price calculator and other information on our pricing page. Further details can be found in our Knowledge Base.

When will the changes be effective?

If you do not currently have a Librato account, the new pricing is effective today.

I am an existing customer; how will this affect me?

If you are an existing customer you have the choice to stay with the current pricing or switch to the new pricing. To help you make the choice we will show you how your charges under the new pricing will differ from those under the old pricing. Once you’ve switched to the new pricing, you cannot go back to the old pricing, but you can stick with the old pricing and decide to switch to the new pricing at a later time. If you do not tell us what you want, we’ll continue to charge you based on the old pricing model.

I’m a trial user, how will this affect me?

At any time during the trial, you will be able to sign up for the Production plan. If you do not sign up for the Production plan during your trial period you will be given a choice to continue under the Production plan or the Developer plan at the end of your trial. If you select the Developer plan you will be able to upgrade to the Production plan later.

If you started your trial before today’s announcement, and prefer to be charged according to the old pricing model or would like to compare your estimated charges under the old and the new pricing model, you can contact us at support@librato.com. We will switch you to the old model if that is what you prefer; like all existing customers, you’ll be able to switch to the new pricing model at a later time.

My trial has expired but I’d like to start using your service, how does this affect me?

The same rules as for current trial users who are at the end of their trial apply for you (see above).

If you have any questions or feedback, please contact us at support@librato.com or stop by in our support chatroom.

Heroku add-on now generally available



I’m happy to announce that our Heroku add-on is out of beta and generally available to all Heroku users! The add-on monitors request performance, sql queries, mail handling, and other key statistics of Heroku applications, with no set-up required, and makes it easy to track any additional custom metrics important to the health of the application, such as running totals, average values, and more. You can add it to any application running on Heroku by following these simple instructions.

The add-on makes it easy to collect application level metrics, since it transparently aggregates metrics from multiple dynos into single contiguous, application level data streams. Beyond that it provides all of the capabilities for storage, analysis, alerting and collaboration our service offers.

Pricing of the add-on is determined by the retention period and the sampling frequency of data streams. You can choose between high resolution (10s) and low resolution (60s) plans and different retention periods. We also have a free “Dev” plan with low (60s) resolution and one day retention.

Heroku is one of our best customers, so we’re especially pleased to now have the add-on available for all of Heroku’s users.

Any feedback you might have is -as always- appreciated; feel free to reach out by email or visit us in our chat room at chat.librato.com.