-
Notifications
You must be signed in to change notification settings - Fork 74
Observability: StackDriver Integration #541
Comments
/assign @ian-mi as I know you have started working on some tracing stuff. |
We should scope this down to multiple issues |
We should make sure that the new Broker implementation support our current SD metrics |
re: the metris list in eventing https://github.com/knative/eventing/issues?q=is%3Aopen+metrics+author%3Anachocano+label%3Aarea%2Fobservability+. IMO we can safely skip it for now, as they were mainly targeting prometheus backends, and we need to explicitly test our SD integration. |
/close Closing as all the release/1, priority/1 issues are closed. All remaining work items still have their own issues that can be prioritized independently. |
@Harwayne: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Problem
High-level issue for Observability related tasks.
TL'DR we should be able to integrate with SD metrics, tracing, and logging.
There has been worked done already in this space. We are mainly lacking Source metrics, as it requires integration with SD backend so that users are not charged. But we need to verify traces and logging are actually working as expected. And maybe move away from span-based tracing if it will simplify things. E2E tests need to be added. Our new Broker impl should also support our current metrics (present in the channel-based one, in the Broker ingress and filter pods), as well as tracing
Metrics
Tracing
Logging
Persona:
Developer
Exit Criteria
Integration with SD metrics in sources, tracing, and logging.
Time Estimate (optional):
???
The text was updated successfully, but these errors were encountered: