Skip to content

Commit f4e9138

Browse files
authored
Update README.md
1 parent 8124634 commit f4e9138

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,7 @@ Provides instrumentation for Kotlin Coroutines. In particular it will trace the
2323

2424
Kotlin-Coroutines-1.0 - all 1.0.x versions.
2525
Kotlin-Coroutines-1.1 - all 1.1.x versions.
26-
Kotlin-Coroutines-1.2 - all 1.2.x versions.
27-
Kotlin-Coroutines-1.3 - all 1.3.x versions.
26+
Kotlin-Coroutines-1.2 - all 1.2.x and 1.3.x versions.
2827
Kotlin-Coroutines-1.4 - all 1.4.x and later versions.
2928

3029
## Installation
@@ -34,6 +33,10 @@ In the New Relic Java Agent directory (directory containing newrelic.jar), creat
3433
Copy the jars into the extensions directory.
3534
Restart the application.
3635

36+
## Verification
37+
The easiest way to see if the instrumentation has been loaded by the Java Agent is to look for the Java Agent UI's Metric Explorer and enter "supportability/weaveinstrumentation/loaded/com.newrelic.instrumentation.labs.kotlin-coroutines". If a metric is reported then the agent has loaded the instrumentation appropriate to the version of Kotlin Coroutines that you are using.
38+
If no metric is displayed, then check for "supportability/weaveinstrumentation/skipped/com.newrelic.instrumentation.labs.kotlin-coroutines". If no metrics are displayed verify that the instrumentation jars have been deployed to the extensions directory and that the user id that runs the application has read access.
39+
3740
## Getting Started
3841

3942
After deployment of the instrumentation jars, you should be able to see the invocation of a coroutine from start to finish across any threads that it executes on.

0 commit comments

Comments
 (0)