Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Splunk Observability Cloud scaler #6190

Open
sschimper-splunk opened this issue Sep 26, 2024 · 1 comment · May be fixed by #6192
Open

Support Splunk Observability Cloud scaler #6190

sschimper-splunk opened this issue Sep 26, 2024 · 1 comment · May be fixed by #6192
Labels
needs-discussion scaler stale All issues that are marked as stale due to inactivity

Comments

@sschimper-splunk
Copy link

Proposal

I've developed a custom scaler for Splunk Observability Cloud to allow for autoscaling based on a series of metrics that can be queried from Splunk Observability Cloud. Documentation is provided in kedacore/keda-docs#1477.

Scaler Source

Splunk Observability Cloud

Scaling Mechanics

Scaling based on a Metric Time Series queried from Splunk Observability Cloud via the SignalFX GO Client.

Authentication Source

Splunk Observability Access Token and Realm to be configured with the TriggerAuthentication resource.

Anything else?

I admittedly am very new to writing Go programs and collaborate with other developers via GitHub. In case I am doing something wrong, please do let me know, and I will fix it.

Copy link

stale bot commented Nov 25, 2024

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

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-discussion scaler stale All issues that are marked as stale due to inactivity
Projects
Status: To Triage
Development

Successfully merging a pull request may close this issue.

1 participant