Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

OpenTelemetry Integration #2280

Closed
phillipgibson opened this issue Jan 11, 2021 · 1 comment
Closed

OpenTelemetry Integration #2280

phillipgibson opened this issue Jan 11, 2021 · 1 comment
Assignees

Comments

@phillipgibson
Copy link
Contributor

Please describe the Improvement and/or Feature Request
Have OSM emit telemetry metrics by utilizing the OpenTelemetry API and SDK. We are aware of Envoy not being supported at this time envoyproxy/envoy#9958.

Scope (please mark with X where applicable)

  • New Functionality [X]
  • Install [ ]
  • SMI Traffic Access Policy [ ]
  • SMI Traffic Specs Policy [ ]
  • SMI Traffic Split Policy [ ]
  • Permissive Traffic Policy [ ]
  • Ingress [ ]
  • Egress [ ]
  • Envoy Control Plane [ ]
  • CLI Tool [ ]
  • Metrics [X]
  • Certificate Management [ ]
  • Sidecar Injection [ ]
  • Logging [ ]
  • Debugging [ ]
  • Tests [ ]
  • CI System [ ]
  • Project Release [ ]

Possible use cases
Having OSM/SMI metrics/telemetry being emitted by the OpenTelemetry specification.

@phillipgibson
Copy link
Contributor Author

We're excited about the OpenTelemetry project and the issues it looks to resolve around standardizing telemetry data. After an assessment to see if it is beneficial for OMS to implement OpenTelemerty, our finding see the project has not matured to a level that would make sense for integration at this point. The lack of Envoy proxy support was a strong factor, since without it we would only be able to emit control plan metrics.

We will revisit this assessment in the near future as more progress is made to OpenTelemetry.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant