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

mqtrigger debugging steps #80

Open
viveksinghggits opened this issue Jun 10, 2019 · 2 comments
Open

mqtrigger debugging steps #80

viveksinghggits opened this issue Jun 10, 2019 · 2 comments

Comments

@viveksinghggits
Copy link

mqtrigger is not able to pick the messages from the configured Kafka Cluster, even though the Kafka Cluster is up and running fine and other clients can produce the message to that Kafka Cluster.
We dont see any logs in that pod also so it becomes increasingly tough to debug the mqtrigger.
We should have some steps documented in this page that explain how can we debug if mqtrigger is not able to pick the Kafka messages and call fission function.

@sanketsudake sanketsudake transferred this issue from fission/docs.fission.io Nov 2, 2021
@sanketsudake
Copy link
Member

@blackfly19 please consider this for update in keda mqtrigger kafka documentation.

@blackfly19
Copy link
Contributor

Sure I'll add it to the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants