Redesign and implement the telemetry framework by r12f · Pull Request #20387 · sonic-net/sonic-mgmt

r12f · 2025-08-24T18:37:04Z

Description of PR

Summary:
Fixes # (issue)

Type of change

Back port request

Approach

What is the motivation for this PR?

The current telemetry framework has many serious problems:

Hard to import, because it is outside of the tests folder
No implementation, hard to try out
Hard to use and extend, because the interface is too primitive
No tests and can break easily

How did you do it?

This PR add a few things to improve the current telemetry framework:

Add new design doc with example code provided in the doc.
Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily.

How did you verify/test it?

Run all tests locally and passed.

Any platform specific information?

N/A.

Supported testbed topology if it's a new test case?

Documentation

mssonicbld · 2025-08-24T18:37:13Z

/azp run

azure-pipelines · 2025-08-24T18:37:27Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-08-24T18:39:12Z

/azp run

azure-pipelines · 2025-08-24T18:39:27Z

Azure Pipelines successfully started running 1 pipeline(s).

wangxin · 2025-08-25T07:03:01Z

The unit test scripts have file name pattern test_*.py. This pattern conflicts with the real feature test scripts. It would be better to rename them to something like ut_*.py.

mssonicbld · 2025-08-30T19:59:45Z

/azp run

azure-pipelines · 2025-08-30T20:00:00Z

Azure Pipelines successfully started running 1 pipeline(s).

r12f · 2025-08-30T20:00:01Z

The unit test scripts have file name pattern test_*.py. This pattern conflicts with the real feature test scripts. It would be better to rename them to something like ut_*.py.

thanks Xin! it is updated now.

r12f · 2025-08-31T00:18:02Z

Need this PR to pass the validate test cases, because the current container is missing the OTEL packages: sonic-net/sonic-buildimage#23855

yutongzhang-microsoft · 2025-09-10T06:27:20Z

Should we add the DB schema to the README?

r12f · 2025-09-11T04:25:46Z

It might be better to add the DB schema in the test report uploader PR. That will be more concrete. : D

Why I did it In order to enable telemetry framework in sonic-mgmt, we will need the open telemetry packages in the sonic-mgmt container: sonic-net/sonic-mgmt#20387 Work item tracking Microsoft ADO (number only): How I did it Updated the Dockerfile.j2. How to verify it Validated by manually install the packages into the mgmt container and run the scripts.

yutongzhang-microsoft · 2025-09-18T02:45:37Z

tests/common/telemetry/reporters/ts_reporter.py

+            return None
+
+        # Create ResourceMetrics with ScopeMetrics
+        scope = InstrumentationScope(


Seems we don't use this variable in the function?

it is used here:

mssonicbld · 2025-09-30T17:25:59Z

/azp run

azure-pipelines · 2025-09-30T17:26:15Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-10-04T22:01:07Z

/azp run

azure-pipelines · 2025-10-04T22:01:22Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-10-08T06:51:27Z

/azp run

r12f · 2025-10-08T06:51:32Z

/azp run

azure-pipelines · 2025-10-08T06:51:38Z

Commenter does not have sufficient privileges for PR 20387 in repo sonic-net/sonic-mgmt

azure-pipelines · 2025-10-08T06:51:41Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-10-09T21:25:06Z

/azp run

azure-pipelines · 2025-10-09T21:25:21Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2025-11-24T05:35:36Z

/azp run

azure-pipelines · 2025-11-24T05:35:51Z

Azure Pipelines successfully started running 1 pipeline(s).

StormLiangMS · 2025-11-27T03:52:02Z

hi @r12f . Questions, when to collect metrics, how long delay will be added? Where to host the metrics data, kusto or other databases?

r12f · 2025-11-27T07:41:05Z

Hi @StormLiangMS , whenever a test completes it will write 1 file for db reporter or send 1 tcp/http request for to reporter. So the delay for each test is at ms level, hence trivial comparing to the test run itself.

The timeseries metrics will be hosted in lab at this moment. And db reporter data will be stored in Kusto via other file parser and separate kusto uploader.

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: vikumarks <vikumar7ks@gmail.com>

Why I did it In order to enable telemetry framework in sonic-mgmt, we will need the open telemetry packages in the sonic-mgmt container: sonic-net/sonic-mgmt#20387 Work item tracking Microsoft ADO (number only): How I did it Updated the Dockerfile.j2. How to verify it Validated by manually install the packages into the mgmt container and run the scripts. Signed-off-by: Feng Pan <fenpan@microsoft.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Dan Caugherty <dcaugher@cisco.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Nishanth Sampath Kumar <nissampa@cisco.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Saravanan <saravanan@nexthop.ai>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Aharon Malkin <amalkin@nvidia.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: YiFan Wang <yifan@nexthop.ai>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Priyansh Tratiya <ptratiya@microsoft.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Lakshmi Yarramaneni <lakshmi@nexthop.ai>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Yael Tzur <ytzur@nvidia.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (sonic-net#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Zhuohui Tan <zhuohui.tan@amd.com>

What is the motivation for this PR? The current telemetry framework has many serious problems: Hard to import, because it is outside of the tests folder No implementation, hard to try out Hard to use and extend, because the interface is too primitive No tests and can break easily How did you do it? This PR add a few things to improve the current telemetry framework: Add new design doc with example code provided in the doc. Implement both TS (timeseries) and DB (database) reporter, so we can try the feature easily. How did you verify/test it? Run all tests locally and passed. Any platform specific information? N/A. Fix TS reporters. Fix TSRepoter. Fix TS reporter. minor fix. Fix example. Reverse relationship of metrics and reporter to support more types of metrics in future. Remove bydesign not working test. Fix example. Update tests. Update TS reporter and DB repoter. Update minor things. Remove no required code. Revert unexpected change. Rename and update doc. * Get os version and job id (#1) Get os version and elastictest job id from correct place. * Revert OS version change. * Remove duplicated mock reporter fixture. --------- Co-authored-by: Yutong Zhang <90831468+yutongzhang-microsoft@users.noreply.github.com> Signed-off-by: Abhishek <abhishek@nexthop.ai>

r12f requested review from a team, wangxin and yxieca as code owners August 24, 2025 18:37

r12f mentioned this pull request Aug 31, 2025

Add open telemetry into sonic-mgmt container. sonic-net/sonic-buildimage#23855

Merged

9 tasks

yutongzhang-microsoft reviewed Sep 18, 2025

View reviewed changes

r12f force-pushed the user/r12f/tel branch from 7c64a37 to 085b441 Compare October 4, 2025 22:01

r12f closed this Oct 8, 2025

r12f reopened this Oct 8, 2025

wangxin approved these changes Nov 26, 2025

View reviewed changes

StormLiangMS merged commit f07430a into sonic-net:master Nov 27, 2025
31 checks passed

anamehra mentioned this pull request Dec 9, 2025

Bug: ConftestImportFailure: NameError: name 'MetricsData' is not defined when opentelemetry is not available #21623

Open

Conversation

r12f commented Aug 24, 2025

Description of PR

Type of change

Back port request

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Uh oh!

mssonicbld commented Aug 24, 2025

Uh oh!

azure-pipelines bot commented Aug 24, 2025

Uh oh!

mssonicbld commented Aug 24, 2025

Uh oh!

azure-pipelines bot commented Aug 24, 2025

Uh oh!

wangxin commented Aug 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mssonicbld commented Aug 30, 2025

Uh oh!

azure-pipelines bot commented Aug 30, 2025

Uh oh!

r12f commented Aug 30, 2025

Uh oh!

r12f commented Aug 31, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

yutongzhang-microsoft commented Sep 10, 2025

Uh oh!

r12f commented Sep 11, 2025

Uh oh!

yutongzhang-microsoft Sep 18, 2025

Choose a reason for hiding this comment

Uh oh!

r12f Sep 28, 2025

Choose a reason for hiding this comment

Uh oh!

mssonicbld commented Sep 30, 2025

Uh oh!

azure-pipelines bot commented Sep 30, 2025

Uh oh!

mssonicbld commented Oct 4, 2025

Uh oh!

azure-pipelines bot commented Oct 4, 2025

Uh oh!

mssonicbld commented Oct 8, 2025

Uh oh!

r12f commented Oct 8, 2025

Uh oh!

azure-pipelines bot commented Oct 8, 2025

Uh oh!

azure-pipelines bot commented Oct 8, 2025

Uh oh!

mssonicbld commented Oct 9, 2025

Uh oh!

azure-pipelines bot commented Oct 9, 2025

Uh oh!

mssonicbld commented Nov 24, 2025

Uh oh!

azure-pipelines bot commented Nov 24, 2025

Uh oh!

StormLiangMS commented Nov 27, 2025

Uh oh!

r12f commented Nov 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

wangxin commented Aug 25, 2025 •

edited

Loading

r12f commented Aug 31, 2025 •

edited

Loading

r12f commented Nov 27, 2025 •

edited

Loading