Skip to content

Commit 95cde46

Browse files
robsundayjaydeluca
andauthored
Update instrumentation/jmx-metrics/javaagent/README.md
Co-authored-by: Jay DeLuca <[email protected]>
1 parent 05b1a3d commit 95cde46

File tree

1 file changed

+6
-6
lines changed
  • instrumentation/jmx-metrics/javaagent

1 file changed

+6
-6
lines changed

instrumentation/jmx-metrics/javaagent/README.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -309,13 +309,13 @@ For now, only the `lowercase` transformation is supported, other additions might
309309

310310
### Unit conversions
311311

312-
Sometimes JMX attributes values are reported in units not aligned with semantic conventions.
313-
For example duration values are usually reported as milliseconds while semantic conventions recommend using seconds.
312+
Sometimes JMX attribute values are reported in units that are not aligned with semantic conventions.
313+
For example, duration values are usually reported as milliseconds while semantic conventions recommend using seconds.
314314

315-
This issue can be solved by providing optional `sourceUnit` metric property together with `unit` metric property.
316-
`sourceUnit` defines native unit of value retrieved from JMX attribute, while `unit` defines the unit of the metric reported to the backend.
317-
If conversion between `sourceUnit` and `unit` is available then it is automatically applied before reporting the metric.
318-
If such a conversion is not available then an error is reported during JMX metrics processing.
315+
This issue can be solved by providing an optional `sourceUnit` metric property together with the `unit` metric property.
316+
`sourceUnit` defines the native unit of value retrieved from JMX attribute, while `unit` defines the unit of the metric reported to the backend.
317+
If a conversion between `sourceUnit` and `unit` is available, then it is automatically applied before reporting the metric.
318+
If such a conversion is not available, then an error is reported during JMX metrics processing.
319319

320320
Currently available unit conversions:
321321

0 commit comments

Comments
 (0)