- ActiveMQ Artemis
- Apache Kafka
- AWS CloudWatch
- AWS Kinesis Stream
- AWS SQS Queue
- Azure Blob Storage
- Azure Event Hubs
- Azure Log Analytics
- Azure Monitor
- Azure Pipelines
- Azure Service Bus
- Azure Storage Queue
- Cassandra
- CPU
- Cron
- Elasticsearch
- External
- External Push
- Google Cloud Platform Pub/Sub
- Graphite
- Huawei Cloudeye
- IBM MQ
- InfluxDB
- Kubernetes Workload
- Liiklus Topic
- Memory
- Metrics API
- MongoDB
- MSSQL
- MySQL
- NATS Streaming
- OpenStack Metric
- OpenStack Swift
- PostgreSQL
- Prometheus
- RabbitMQ Queue
- Redis Lists
- Redis Lists (supports Redis Cluster)
- Redis Lists (supports Redis Sentinel)
- Redis Streams
- Redis Streams (supports Redis Cluster)
- Redis Streams (supports Redis Sentinel)
- Selenium Grid Scaler
- Solace PubSub+ Event Broker
Troubleshooting Click here for latest
KEDA logging and telemetry
The first place to look if something isn’t behaving correctly is the logs generated from KEDA. After deploying you should have a pod with two containers running within the namespace (by default: keda).
You can view the KEDA operator pod via kubectl:
kubectl get pods -n keda
You can view the logs for the keda operator container with the following:
kubectl logs -n keda {keda-pod-name} -c keda-operator
Reporting issues
If you are having issues or hitting a potential bug, please file an issue in the KEDA GitHub repo with details, logs, and steps to reproduce the behavior.