You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[connector/spanmetrics] Fix spanmetrics for child spans (#36718)
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Currently, metric start timestamps are associated with the parent span
(resource level). This means that all child spans, even those that occur
asynchronously or infrequently, inherit the same start timestamp. This
can lead to inaccurate data.
This merge request proposes moving the start timestamp (and last seen
timestamp) from the parent span level to the individual child span
(metric) level. This will ensure that each metric has its own accurate
start and last seen timestamps, regardless of its relationship to other
spans.
<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes#35994
<!--Describe what testing was performed and which tests were added.-->
#### Testing
<!--Describe the documentation added.-->
#### Documentation
<!--Please delete paragraphs that you did not use before submitting.-->
---------
Co-authored-by: Antoine Toulme <[email protected]>
Co-authored-by: Murphy Chen <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Yang Song <[email protected]>
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: bug_fix
5
+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
6
+
component: connector/spanmetrics
7
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8
+
note: This change proposes moving the start timestamp (and last seen timestamp) from the resourceMetrics level to the individual metrics level. This will ensure that each metric has its own accurate start and last seen timestamps, regardless of its relationship to other spans.
9
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
10
+
issues: [35994]
11
+
# (Optional) One or more lines of additional information to render under the primary note.
12
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
13
+
# Use pipe (|) for multiline entries.
14
+
subtext:
15
+
# If your change doesn't affect end users or the exported elements of any package,
16
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
17
+
# Optional: The change log or logs in which this entry should be included.
18
+
# e.g. '[user]' or '[user, api]'
19
+
# Include 'user' if the change is relevant to end users.
20
+
# Include 'api' if there is a change to a library API.
0 commit comments