Telemetry - Invoke services dont have plugin context or structured event
See original GitHub issueWhen running a service plugin like superset that blocks for a long time and is then exited using CTRL+C I’m not able to track the plugin context. I think whats happening is:
meltano invoke superset:ui
(blocking)- CLI started event fired when started up. Plugin context isnt available yet
- build dashboards
- CTRL+C
- <MISSING CLI completed/aborted/etc. with plugin context>
- <MISSING structured legacy event>
I think the fact that I need to CTRL+C to close the blocking service plugin means the structured event isnt fire because its not a successful exit and with the new unstructured events we dont get a plugin context. I dont get enough info for these events to be useful, all I know its that invoke
ran but nothing about what plugin/command (i.e. ui
)/etc. This is likely undercounting usage of Airflow also because we never get to the successful firing of structured events either.
Would it be possible to include the plugin context on the first event?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Supporting Real User Monitoring Events in OpenTelemetry ...
This is a proposal to add real user monitoring (RUM) as an independent observability tool, or 'signal', to the Open Telemetry specification.
Read more >Azure Application Insights for JavaScript web apps
We continue to assess the viability of OpenTelemetry for browser scenarios. ... If you don't already have a resource and connection string, ...
Read more >open-telemetry/opentelemetry-node - Gitter
I'm looking forward to when open telemetry, uniform error handling, and structured logging with consistent log-levels between products are fully supported ...
Read more >Context Management in OpenTelemetry NodeJS | by Amir B
This post shares some of our experience gained by writing nodejs plugins and debugging context issues at Aspecto.
Read more >Configure Model-driven Telemetry on Cisco IOS-XE Devices ...
Knowledge of YANG is needed to understand the data that is required when using telemetry. Knowledge of NETCONF operations, such as get, get- ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@pnadolny13 ok hotfix in bound.
I can’t think of any cases off the top of my head where we’d need to unbind a context. As long as we stick our pattern of binding PluginContexts to the events/things actually using them. i.e. in
meltano run
plugin context is related to the block events, inetl
its related to the cli event.