Update naming.md to clarify 'duration' definition#3543
Open
lahabana wants to merge 5 commits intoopen-telemetry:mainfrom
Open
Update naming.md to clarify 'duration' definition#3543lahabana wants to merge 5 commits intoopen-telemetry:mainfrom
lahabana wants to merge 5 commits intoopen-telemetry:mainfrom
Conversation
**time** and **duration** are close but slightly different ways to instrument times. There are plenty of examples in this doc with **duration** yet it wasn't defined in the instrument naming section. @jack-berg explained in [this comment](open-telemetry#816 (comment)) clearly the difference between **time** and **duration**. This attempts to update the documentation to persist this information by documenting **duration** and explaining when to use it compared to **time**. Part of open-telemetry#816
lmolkova
reviewed
Mar 14, 2026
Member
lmolkova
left a comment
There was a problem hiding this comment.
Thanks for the clarification, it makes sense, just left some comments to make it more precise
Co-authored-by: Liudmila Molkova <neskazu@gmail.com>
Author
|
Thanks for clarifying @lmolkova I've included your suggestions. |
lmolkova
reviewed
Mar 16, 2026
Co-authored-by: Liudmila Molkova <neskazu@gmail.com>
Author
|
@lmolkova updated. Changelog fails does it really make sense to add an entry in the Changelog for this? |
lmolkova
approved these changes
Mar 25, 2026
kamphaus
reviewed
Mar 25, 2026
This reverts commit 4b8ce00.
Signed-off-by: Charly Molter <charly.molter@konghq.com>
lmolkova
approved these changes
Apr 3, 2026
trask
approved these changes
Apr 3, 2026
| should be called `{operation name}.duration`. | ||
| For example, `http.server.request.duration` for the time taken to process each HTTP request. | ||
| The difference with `time` is that `time` is used to measure monotonically increasing total time, | ||
| whereas `duration` captures the aggregated elapsed time. |
Member
There was a problem hiding this comment.
the word "aggregated" is a bit confusing here, maybe something like
Suggested change
| whereas `duration` captures the aggregated elapsed time. | |
| whereas `duration` captures the elapsed time of discrete operations |
Member
@lahabana no need, I added label to skip changelog, adding [chore] to the title would also do the job |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #816
Changes
time and duration are close but slightly different ways to instrument times.
There are plenty of examples in this doc with duration yet it wasn't defined in the instrument naming section.
@jack-berg explained in this comment clearly the difference between time and duration.
This attempts to update the documentation to persist this information by documenting duration and explaining when to use it compared to time.
Merge requirement checklist
[chore]