Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Install Instructions #115

Merged
merged 2 commits into from
Jan 31, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,11 +27,14 @@ implementations communicating via HTTP using the okhttp libraries, respectively.
## Start the reporter

Early in the lifecycle of your application, you will want to create and
start a `NewRelicReporter`.
start a `NewRelicReporter`. This should be created after the `MetricRegistry` is created and before any metrics have been generated.

The `YOUR_SECRET_API_KEY` is referring to your New Relic Event API insert key or license key.
For more information and how to obtain a key, [visit our docs](https://docs.newrelic.com/docs/insights/insights-data-sources/custom-data/send-custom-events-event-api#register).

The `METRIC_INGEST_URI` is the ingest endpoint for collected metrics. The default value will point to the US Production ingest endpoint.
For additional information on alternative ingest endpoints, [visit our docs](https://docs.newrelic.com/docs/apm/agents/java-agent/configuration/java-agent-configuration-config-file/#metric_ingest_uri).

```
MetricRegistry metricRegistry = new MetricRegistry(); // If you're already using dropwizard-metrics you may already have one of these.
...
Expand Down
Loading