• Log inStart now

On August 31, 2024, we're EOLing developer.newrelic.com. All relevant content has been migrated to docs.newrelic.com.

Send telemetry data to New Relic


This procedure is a part of course that teaches you how to build a quickstart. If you haven't already, checkout the course introduction.

Each procedure in this course builds on top of the last one, so make sure you deploy your application before proceeding with this one.

The first step in the process of building a quickstart is instrumenting your library or configuring your platform to send telemetry data to New Relic. Once you set this up, your product's users will be able to start seeing that data in their account.

Setting up your product to allow your users to easily send data from your product to New Relic is important because the quickstart you'll offer them will use it in dashboards, alerts, or other resources you provide. Once your user can see the data, they'll be able to use your quickstart to visualize it and gain actionable insights in a matter of minutes.

Telemetry data types

You need to send at least one type of telemetry data to New Relic from your library or platform in order to build an effective quickstart. New Relic supports four telemetry data types:

  • Metrics: Metrics are aggregated measurements of your system's performance and behaviors. If your product is a database, you might send metrics like CPU utilization, memory utilization, and query throughput. Note that metrics are generally only used if you want to limit the amount of Data sent to New Relic. Note that many metrics, such as error rates and throughput, can be computed by aggregating events.
  • Events: Events capture things that occur in your product. If your platform automates application deployments, you might generate an event every time a job runs. If your application scans for security vulnerabilities, you might generate an event every time you detect one.
  • Logs: Logs are time-based text records that help your users see what's happening in your system.
  • Traces: Traces capture details of a single request as it moves through a system.


This procedure is a part of course that teaches you how to build a quickstart. Continue to next lesson, send metrics from your product.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.