• /
  • Log in
  • Free account

Data formatter: Set default formats for numeric values


As of April 12, 2021, we are upgrading Insights to an improved web and mobile experience! All of your Insights URLs will be redirected automatically to the corresponding dashboards in New Relic One. For more details about this migration and how you can easily plan for this transition, see our Explorers Hub post.

Use New Relic's data formatter to configure default formats for attributes with numeric values by specifying rounding, comma usage, the number of digits past the decimal point, etc. These settings affect how data appears in your New Relic Insights dashboards on an account-wide basis.

Format your numbers

To access the data formatter: Go to insights.newrelic.com > Manage data > Formatter. Then, to format your numbers:

  1. Select an event type.
  2. Select an attribute from the list.
  3. Select a data type.
  4. Optional: Select additional formatting information for the attribute.


A quoted numeric string is a string, not a number. The data formatter does not support formatting strings.

Data types

Data type



New Relic Insights will attempt to select the format on a per-value basis.


The value represent a duration in relative units of time (for example, less than 5 seconds)


The value represents numeric data. It can be formatted with commas, precision, etc. Commas will be added automatically as thousands separators.

Selecting this option provides an additional dropdown to specify formatting options:

  • humanize: The data formatter will attempt to round fractional components to the significant digits, up to five decimal places. For example, 1.20003 would be rounded to 1.2.
  • 0 - 4: Select 0 to 4 to specify the number of significant digits after the decimal point.


The value represents a time formatted as seconds or milliseconds since UNIX epoch.

Unique ID

The value represents a unique numeric ID that you do not want to be formatted.


To avoid problems identifying numeric data as unique numeric IDs (such as commas separating thousands in the ID string), always set these manually. Or, to help identify that the value is not intended for computation, store it as a string instead of a number by wrapping it in quotes.

For more help

Create issueEdit page
Copyright © 2021 New Relic Inc.