Create additional metric providers

keptn / lifecycle-toolkit

Toolkit for cloud-native application lifecycle management

https://keptn.sh

Apache License 2.0

307 stars 122 forks source link

Create additional metric providers #745

Open StackScribe opened 1 year ago

StackScribe commented 1 year ago

Goal

The Keptn Metrics Operator is currently supporting Prometheus and Dynatrace as Metrics Providers. To allow a broader range of observability providers, additional integrations should be provided.

Technical Details

Additional Metrics providers for KeptnMetrics should be provided (example: https://github.com/keptn/lifecycle-toolkit/tree/main/operator/controllers/common/providers)
This might be: Prometheus Exporters, Sentry, Datadog, Nagios, Icinga, Zabbix, ...

DoD

[ ] Documentation is updated under https://github.com/keptn/lifecycle-toolkit/blob/main/metrics-operator/README.md#contributing that describes how to implement the interface and what each parameter is useful for

heckelmann commented 1 year ago

I would suggest having a generic API provider as well like keda does (https://keda.sh/docs/2.9/scalers/metrics-api/).

octonawish-akcodes commented 1 year ago

I am interested in this how can I get started any resources and slack link?

ShivangShandilya commented 1 year ago

Regards @thschue @RealAnna. I'm pretty intrigued with this project, any pointers on how can I start with this??

ronitblenz commented 1 year ago

I am interested to start a proposal in this project. It would be convenient if I knew the process of application/writing proposal. Slack/Discord channel for communication is also appreciated !

thisthat commented 1 year ago

Hey all! I agree with @heckelmann: a generic API provider should be implemented. This way, based on an URL and API token (optional) we could get multiple providers out-of-the-box.

For resource on how to implement this, please have a look at https://github.com/keptn/lifecycle-toolkit/issues/554 and its related PR

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.