This issue is to explore and discuss integrating the Prometheus ecosystem into the explorer.
When referring to "the prometheus ecosystem", we mean Prometheus exporters and SDKs, both from the official prometheus project but also including community driven projects, like https://github.com/swift-server/swift-prometheus.
The ecosystems we have integrated thus far have come from official opentelemetry projects, and are mostly monolithic sources / repos that we scrape metadata from, therefore ensuring everything remains up to date automatically.
This contrasts the prometheus ecosystem where it will more distributed, and likely rely on crowd sourcing information, and might not have mechanisms for scraping or having automation to ensure things are up to date.
There is existing art - pages like https://prometheus.io/docs/instrumenting/exporters/ - but it can be difficult to maintain, for many of the reasons stated above around having a way to ensure things are up to date.
So some questions to begin with:
- How to decide what should and can be included in the registry (or if there needs to be criteria at all)
- What categories or types of components should be included (SDKs, exporters... anything else)
- What information / metadata would be useful for these components
- How would the information be sourced and kept up to date
cc: @ArthurSens
This issue is to explore and discuss integrating the Prometheus ecosystem into the explorer.
When referring to "the prometheus ecosystem", we mean Prometheus exporters and SDKs, both from the official prometheus project but also including community driven projects, like https://github.com/swift-server/swift-prometheus.
The ecosystems we have integrated thus far have come from official opentelemetry projects, and are mostly monolithic sources / repos that we scrape metadata from, therefore ensuring everything remains up to date automatically.
This contrasts the prometheus ecosystem where it will more distributed, and likely rely on crowd sourcing information, and might not have mechanisms for scraping or having automation to ensure things are up to date.
There is existing art - pages like https://prometheus.io/docs/instrumenting/exporters/ - but it can be difficult to maintain, for many of the reasons stated above around having a way to ensure things are up to date.
So some questions to begin with:
cc: @ArthurSens