-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: remote tap extension #19634
Comments
I will sponsor this component! |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
I am restarting this work, and have created a PR to get this in, cutting down the original contribution to a skeleton so we can get it in before we discuss the implementation. See #27477. |
I think the way this extension will run might be by being linked from processors which will self-register on startup based on configuration. Meaning, each processor will be able to list one or more extensions to report in:
This will allow to report data back. This also enables other extensions to perform this function. |
**Description:** Adds the basis of a new extension, the remote ~observer~ tap extension, to be used to display the contents of the data observed via remote observer processors. This PR deals only with the structure and required files related to the extension. **Link to tracking Issue:** #19634 **Testing:** N/A **Documentation:** README --------- Co-authored-by: Pablo Collins <[email protected]>
**Description:** Adds the basis of a new extension, the remote ~observer~ tap extension, to be used to display the contents of the data observed via remote observer processors. This PR deals only with the structure and required files related to the extension. **Link to tracking Issue:** open-telemetry#19634 **Testing:** N/A **Documentation:** README --------- Co-authored-by: Pablo Collins <[email protected]>
**Description:** Adds the basis of a new extension, the remote ~observer~ tap extension, to be used to display the contents of the data observed via remote observer processors. This PR deals only with the structure and required files related to the extension. **Link to tracking Issue:** open-telemetry#19634 **Testing:** N/A **Documentation:** README --------- Co-authored-by: Pablo Collins <[email protected]>
Closing as the initial contribution is in. |
The purpose and use-cases of the new component
The websocket viewer extension provides a web-based user interface that allows users to view the data received by all registered websocket processors (issue #19633) in real-time. The extension can be accessed by opening the web page provided by the extension on a web browser, which will display a table or a dashboard with the data received by each processor.
When the Collector starts up, any configured websocket processor will automatically connect to the extension and register itself. The extension will then aggregate the data from all connected processors and display it in a structured and user-friendly way.
The websocket viewer extension can be used for a variety of use cases, including:
Troubleshooting: Operators can use the extension to monitor the data exchanged between components and identify problems.
Learning: Users can use the extension to explore the data generated by different components and learn how the components work and interact with each other.
A POC can be found here.
Example configuration for the component
Telemetry data types supported
Metrics, traces, and logs.
Is this a vendor-specific component?
Sponsor (optional)
@atoulme
Additional context
No response
The text was updated successfully, but these errors were encountered: