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
Hello, @christophe-kamphaus-jemmic! I'm here to help you with any bugs, questions, or contributions you may have. Feel free to ask me anything while you wait for a human maintainer.
To enable DevLake to process incoming CI/CD events via the OpenTelemetry protocol (OTLP), similar functionality to the existing webhook plugin would need to be implemented. This would involve creating a receiver that can handle OTLP data, aligning with the OpenTelemetry Semantic Conventions for CI/CD. The architecture would need to support the ingestion, transformation, and storage of OTLP data, similar to how the webhook plugin processes JSON payloads for incidents and deployments [1].
Key components that might require modification include:
Data Ingestion Layer: Implementing an OTLP receiver to accept and process incoming CI/CD events.
Data Transformation and Storage: Adapting the existing dataflow process to handle OTLP data, ensuring it fits into the Raw, Tool, and Domain layers of DevLake's architecture [2].
Metrics and Analytics: Extending the analytics capabilities to support metrics derived from OTLP data, potentially leveraging the work of the CI/CD Observability SIG to ensure compatibility with emerging standards.
This approach would allow DevLake to integrate with the broader OpenTelemetry ecosystem, supporting standardized observability practices in CI/CD environments.
Question
What would be needed for DevLake to be able to process incoming CICD events via the OpenTelemetry protocol (otlp)?
I suppose that it could work similar to the webhook plugin.
Additional context
The OpenTelemetry Semantic Conventions SIG for CICD is working on defining CICD signals in OpenTelemetry.
https://www.cncf.io/blog/2024/11/04/opentelemetry-is-expanding-into-ci-cd-observability/
The text was updated successfully, but these errors were encountered: