From e492f8902e3e8b66e70990d6d056de6f54e84a2e Mon Sep 17 00:00:00 2001
From: edeleon <edeleon@newrelic.com>
Date: Tue, 30 Jan 2024 09:14:53 -0800
Subject: [PATCH] added more detail on when to create a NewRelicReporter

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 85344ae..94a3ad6 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,7 @@ 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).