Docs » Administration » Viewing Billing and Usage Information

Viewing Billing and Usage Information 🔗

Note

The information in this document applies to organizations whose subscription plan is based on the number of hosts or metrics that SignalFx is monitoring for you. If your organization’s usage is based on the rate at which you are sending datapoints to SignalFx (DPM), see View Usage Information (DPM plans only).

Overview 🔗

Admin users in your SignalFx organization can view the billing and usage information for the organization as a whole. SignalFx provides summary and detail reports to help you understand and manage the data SignalFx is monitoring for you. In addition to counts for hosts and containers, the reports also contain counts for custom, bundled, and high-resolution metrics.

About custom, bundled, and high-resolution metrics 🔗

What are the differences between host, container, bundled, and custom metrics? 🔗

Host and container metrics are the metrics sent by default by the SignalFx Smart Agent, or via SignalFx’s public cloud integrations, for hosts, containers and the services running on them.

Bundled metrics are additional metrics sent via SignalFx’s public cloud integrations that are not attributed to specific hosts or containers. They are included as part of a host-based subscription, and you are not charged for them.

Custom metrics are those metrics reported to SignalFx outside of host, container or bundled metrics. Custom metrics are often used for application monitoring, such as counting the number of API calls or measuring the duration of API requests, but may also include system or service metrics that you configure the SignalFx Smart Agent to send, outside of its default set of metrics. Your SignalFx subscription allows you to send a certain number of custom metrics.

Note that in this context, the term “metric” actually refers to what is generally called a metric time series, or MTS.

How are high-resolution metrics different from standard-resolution metrics? 🔗

Metrics that are not designated as high resolution are processed by SignalFx at the coarser of their native resolution or 10-second resolution. In other words, they are never displayed at a resolution finer than 10 seconds.

In contrast, high-resolution metrics are processed by SignalFx at their native resolution or at 1-second resolution (whichever is coarser). High-resolution metrics enable exceptionally fine-grained and low-latency visibility and alerting for your infrastructure, applications and business performance. Your SignalFx subscription allows you to send a certain number of high-resolution metrics.

Note that in this context, the term “metric” actually refers to what is generally called a metric time series, or MTS.

Using the Billing and Usage page 🔗

To view available usage reports, open the Settings menu at far right on the navigation bar, hover over Organization Settings, and then select Billing & Usage (available only for SignalFx administrators). You see a chart showing your current usage numbers for hosts, containers, custom metrics, and high-resolution metrics.

../_images/current-usage.png

Below the chart, you may see additional charts representing usage trends that you can customize to show different data or different time periods.

To view usage reports available for download, click Usage Reports. The reports available on the Billed Usage tab are shown. Different reports are available on the Usage Breakdown tab.

../_images/billed-usage.png

Clicking on the icon for a report downloads the report. (In some browsers, you might have to right click on the icon and save the report.) All reports are tab-separated text files. They are designed to be imported into a spreadsheet application, such as Microsoft Excel, Google Sheets or Apple Numbers.

Tip

If you have switched from a DPM-based subscription plan to a plan that is based on the number of hosts or metrics that SignalFx is monitoring for you, older reports on the Billed Usage tab indicate that they represent DPM-based data. Reports on the Usage Breakdown tab are not available for dates prior to changing your subscription.

Monthly Usage Report 🔗

This report is available on the Billed Usage tab. For each hour within the month (or month to date, for the current month), this report shows the number of hosts and containers being monitored, and the number of custom metrics and high-resolution metrics being sent to SignalFx. It follows your billing period, and uses the month in which a billing period starts as the label in the report link. For example, if your billing period starts on the 10th of the month, then a link for ‘March 2018’ covers the period of March 10 through April 9, 2018.

The report has 6 columns:

  • Date

    Follows the mm/dd/yy format

  • Hour Ending

    Follows the 24 hour hh:mm UTC format. For example, 01:00 indicates the hour from midnight to 1:00 AM UTC.

  • # Hosts

    The number of hosts that sent data during the specified hour

  • # Containers

    The number of containers that SignalFx monitored during the specified hour

  • # Custom Metrics

    The number of non-high-resolution custom metrics (MTS) that were sent to SignalFx during the specified hour

  • # High Res Metrics

    The number of high-resolution metrics (MTS) that were sent to SignalFx during the specified hour

In general, this report is useful if you want to determine whether your usage is in line with your subscription plan. Using the data, it is easy for you to calculate your average usage, how many hours in the month you have been over or under your plan, and by how much.

Monthly Usage Report (Multiple Organizations) 🔗

If you are working in a SignalFx organization that has multiple organizations associated with your subscription, an option for a summary report that includes information on multiple organizations is also available. Like the Monthly Usage Report, this report shows hourly information for hosts, containers, custom metrics, and high-resolution custom metrics. However, this report also includes this data for each organization associated with your subscription.

Downloadable Dimension Report 🔗

This report, available on the Usage Breakdown tab, shows information on MTS associated with datapoints sent from hosts or containers, as well as information related to custom, high-resolution, and bundled MTS. It breaks down the totals by dimension, so you can see where data is coming from.

The Dimension Report is useful for understanding the nature of the data your organization is sending so you can tune it accordingly. For example, you might see some dimensions (such as environment:lab) that indicate you are sending data for hosts or services that you don’t care to monitor using SignalFx.

You can select or type in a date for this report. All values in the report are based on the 24‑hour period (in UTC) for the date.

The report has 22 columns: two for dimension name and value, and four for each type of usage metric (host, container, custom, high resolution, or bundled). The following illustration shows a portion of the report, including data for host, container, and custom metrics. (If you are on a custom metrics subscription plan, you won’t see columns for host or container metrics in your report.)

../_images/dimension-report.png
  • Dimension Name and Dimension Value

    Dimension Name and Dimension Value are the key/value pairs of the dimensions that are sent in with your metrics. Unique combinations of dimensions and metrics are represented as metric time series (MTS) in SignalFx. The values in each row represent counts associated with the MTS for the specified dimension name and value.

  • No. [usage metric] MTS

    During the report’s 24-hour period (UTC), the number of unique MTS for which at least one datapoint was received from a host or a container; the number of custom, high-resolution, or bundled MTS.

  • New [usage metric] MTS

    During the report’s 24-hour period (UTC), the number of unique MTS for which data was received from a host or a container on that date for the first time; the number of custom metrics, high-resolution, or bundled MTS associated with data that was received on that date for the first time.

  • Avg [usage metric] MTS Resolution

    The average reporting frequency (native resolution) of the datapoints comprising the MTS. This value is averaged across the number of MTS, and over the course of the 24‑hour period represented by the date of the report. For example, a value of 10 means the data is being sent every 10 seconds, i.e. has a 10s native resolution; a value of 300 means that the data is being sent every 5 minutes, i.e. has a 5m native resolution, as is the case with standard AWS CloudWatch metrics.

    This value is calculated as an average across all of the MTS associated with the relevant dimension value. As a result, it may contain outliers (e.g. an MTS that is reporting more slowly or with greater jitter or lag) that skew the average. For example, for data being sent every 5 minutes (300 seconds), you might see a value of 280, or a value of 315. This value should be treated as an approximate number that guides what you do with your metrics, rather than a way of auditing the precise timing of them.

  • No. [usage metric] Datapoints

    During the report’s 24-hour period (UTC), the number of datapoints received by SignalFx from hosts or containers; the number of datapoints associated with custom, high-resolution, or bundled MTS.

Downloadable Custom Metric Report 🔗

This report, available on the Usage Breakdown tab, shows information on MTS associated with datapoints sent from hosts or containers, as well as information related to custom, high-resolution, and bundled MTS, for a specified date. The content of most columns in this report represents the same kinds of values as the Downloadable Dimension Report, except that the information is broken down by metric name instead of by dimension name and value. Therefore, you can see how SignalFx is categorizing data associated with each individual metric.

A significant difference about this report is in how you can use the No. Custom MTS column. If there is a non-zero value in this column, the metric is designated as a custom metric, and all MTS for this metric are counted towards the quota associated with your SignalFx plan. Knowing how many custom MTS your organization is sending can help you tune your usage accordingly. For example, you might notice that there are some custom metrics that you no longer want to report to SignalFx. Conversely, you might decide to increase the number of custom metrics in your plan, so you can avoid overage charges. (You can use the No. High Resolution MTS column in the same way.)

About older report formats 🔗

The Downloadable Dimension Report is a revised format of the report formerly called the Metrics by Dimension report. If you select a date for the Dimension report that is earlier than the release of the new format, the report you download will be formatted like the older Metrics by Dimension report. The old report format provides an aggregate view of the data; that is, it doesn’t show separate values for different types of usage metrics (host, container, etc.).