Supported Data Types
📈 MetricsOverview
The New Relic source accepts metrics from the New Relic Metric API and the New Relic Agent protocol. Metric API payloads are received onmetrics_path, and Agent payloads use agent_base_path with a method query parameter.
Configuration
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| Name | String | none | true | Unique identifier within Sawmills. |
| Endpoint | String | 0.0.0.0:14275 | true | HTTP listen address for New Relic payloads. |
| Metrics Path | String | /metric/v1 | true | Path for New Relic Metric API requests. |
| Agent Base Path | String | /agent_listener/invoke_raw_method | true | Path for New Relic Agent protocol requests. |
| Agent Endpoint | String | https://collector.newrelic.com/agent_listener/invoke_raw_method | true | Upstream New Relic agent endpoint used to proxy preconnect and connect. |
Send metrics to the collector
Point your app’s New Relic endpoints at the Sawmills collector. You need to configure two environment variables:| Variable | Controls | Format | Example |
|---|---|---|---|
NEW_RELIC_HOST | Java agent (timeslice metrics) | host:port | <collector-id>.collectors.sawmills.ai:10000 |
NEW_RELIC_METRICS_HOST | Telemetry SDK (dimensional metrics) | https://host:port | https://<collector-id>.collectors.sawmills.ai:10000 |
<collector-id> is shown in the Sawmills UI under your pipeline’s collector details.
For a full Java app walkthrough, see How to send data from a New Relic Java app.
Minimal Telemetry SDK example:
Metric API Format
Supported metric types:gaugecount(requiresinterval.ms)summary
Agent Protocol
Supported methods:preconnectconnectmetric_data
countsumminandmax(as quantiles 0 and 1)sawmills.scopeattribute when presentsawmills.exclusive_timeattributesawmills.sum_squaresattribute