Quick Setup

Simply connect your AWS account to your Instrumental project, select your desired AWS services, and then jumpstart your project with our premade dashboards and graphs for each service.

Fast Ingestion

Unlike other monitoring platforms, CloudWatch data generally appears in under two minutes. Instrumental uses the latest CloudWatch APIs and a high-scale infrastructure to import your metrics with minimal delay.

Transparent Pricing

You'll receive upfront pricing estimates including any impact on your AWS costs. Free plans provide up to 500 metrics, and Production plans are available for only $0.0034/metric/day.

Highly Configurable

You can adjust the frequency of metric collection for services and metrics, and you can select which regions to support. Fewer metrics equate to lower costs, while more metrics means more valuable data.

More Joy, Less Frustration

Freedom from the AWS Console

Quickly explore and troubleshoot your application performance without logging into AWS or digging through the CloudWatch interface.

Easy Metric Entry

Add metrics in one step with a simple textbox with auto-complete, wildcards, and query language functions.

Lightning Fast

With quick response times and keyboard shortcuts, Instrumental was purposely built be fast and accessible..

Power at Your Fingertips


Sharing knowledge about the state of your application is as critical as having the knowledge in the first place. Instrumental makes it fast and simple to share data—internally and externally.

Query Language

With the Instrumental Query Language, you can transform, aggregate, and time-shift data to get the perfect visualization of exactly what's happening in your application.

Intelligent Alerts

Instrumental goes beyond email and text notifications with webhooks that can call scripts and Lambda functions (in combination with API Gateway) to take action based on your application's status.

High-Resolution Data

All production plans include over a year of data storage at full, one-minute resolution. Instrumental won’t aggregate or downscale your data over time, allowing for accurate yearly comparisons.

Complete Performance Visibility

CloudWatch Metrics

Instrumental's integration automatically imports 150+ CloudWatch metrics across major AWS services including EC2, RDS, and Lambda. For a full list of supported services and metrics, see the CloudWatch integration documentation.

Application Metrics

Monitor your application with any of our agents, or your existing StatsD or Statsite setup.

Server & Service Metrics

The InstrumentalD daemon automatically collects metrics from your servers and services.

Pricing that Scales

Pricing based on what you choose to measure, not arbitrary technical details like volume or hosts.


    Up to 500 Metrics
    3 Hours of Data Visibility


    Unlimited Metrics
    13 Months of Data Visibility
    metric / day


    Need 50k+ metrics?
    Need more throughput?

Pay for What You Use

With Instrumental, you only pay for metrics. No counting hosts, no worrying about volume, no counting team members. You should pay to know, not to grow.

No Throughput Anxiety

Sending the same metric thousands of times per minute? No problem! Over a million datapoints flow through Instrumental every second. Every Production Plan includes up to a billion datapoints per day.

Proven Reliability

Instrumental is trusted by companies of all sizes, from startups to large enterprises.

Pricing FAQ

What is a metric?

A metric is a uniquely named set of datapoints. Metric names are strings that conform to a particular pattern and are used to access datapoints on graphs, dashboards, and alerts. Here's an example: Let's say you have 2 web servers, and you use InstrumentalD to collect system metrics. You'll have 3 load metrics per server, or 6 metrics:

  • system.server-001.load.load1
  • system.server-001.load.load5
  • system.server-001.load.load15
  • system.server-002.load.load1
  • system.server-002.load.load5
  • system.server-002.load.load15

The more information you want to include about a given set of datapoints, the more unique metrics you may have. Let's say you're using one of our agents to collect custom application metrics for an invoicing tool. You'll want to track invoice creation, which you could do with 1 metric, say app.invoice.created. That's 1 metric, even if you create 100,000 invoices. If you want to track invoice creation per user (e.g, app.invoice.created.user-1, app.invoice.created.user-2, etc.), then you'll have 1 metric for each user that created invoices during the billing period.

Want to learn more? Read more about metrics in the docs, or message support with any questions.

What is a datapoint?

A datapoint is a single value for a metric. Let's say you have a metric tracking signups in your application, app.signups. Each signup would represent a single datapoint. Since Instrumental doesn't charge based on datapoints (also known as volume), you'll only be billed for 1 metric, even if everyone on the planet signs up for your service in the same week.

Every production plan includes up to 1 billion datapoints per day. If you think you'll need more than that, just let us know.

How do you decide how many metrics I have?

We only bill for active metrics. A metric is active when a datapoint is received for that metric. You should feel free to add and remove metrics while debugging technical issues, since these will not have any long-term pricing impact.

How does invoicing work?

Since we bill based on active metrics, Instrumental billing is backward-looking. At the end of your billing period, we calculate the number of active metrics per day during the period and multiply by your plan's price-per-metric. To avoid surprises, we will notify you if we detect a significant increase in your metric usage.

How many metrics will I use?

That depends! We generally recommend that everyone have visibility into servers, external systems, application performance, and the most important key functions of your application.

Basic server monitoring using InstrumentalD takes about 30 metrics per server, depending on the number of disks and network adapters. Using InstrumentalD to monitor services like MySQL and Redis is 5-20 metrics per instance, depending on the service. Basic application monitoring using Metrician creates 10 metrics but can easily be configured to collect many more. Custom application monitoring varies widely depending on your goals and how much information you want to gather. This can be 0 or hundreds of metrics.

There are also many open source tools that can be configured to send metrics to Instrumental, like statsd and telegraf. The number of metrics gathered by those tools varies widely and is based on what they measure and how they’re configured.

The best way to answer this question is to sign up and start sending metrics. Every development plan includes 500 free metrics so you try Instrumental without risk. Feel free to get in touch with us if you’d like to get a more specific estimate of your potential usage.

What if I accidentally send too much data?

The 1 billion datapoint limit is a soft limit, and few customers ever reach it. If you do send more datapoints than your plan allows, we’ll message you to discuss options. If necessary, we may sample your incoming data to reduce your volume below your plan level.

There’s no limit on the number of metrics you can send. However, we understand that it’s sometimes easy to send more metrics than you intend. We don’t want anyone to get a surprising bill at the end of the month, so we message you if your metric usage increases quickly.

Is my data secure?

Instrumental goes above and beyond industry standard best practices for protecting your personal data at all levels of the organization including the electronic transfer of data. While Instrumental monitoring data does not inherently contain personally-identifiable data, we still protect all data with the same level of care.

How long do you keep my data?

We store 13 months of data, which means you can analyze 12 complete months of data at a time.

Questions? We can help!