-
Notifications
You must be signed in to change notification settings - Fork 49
WILDCARDs and TLS configuration added #61
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
Conversation
CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
mathsman5133
commented
Apr 28, 2023
Hi, this would be fantastic - is there any update?
mampersat
commented
Nov 6, 2023
+1
mampersat
commented
Nov 9, 2023
Recommend changing this line , adding the TCPS scheme
Current:
tooltip="Supported schemes: TCP (tcp://), TLS (tls://), or WebSocket (ws://)"
Suggested:
tooltip="Supported schemes: TCP (tcp://), TCPS (tcps://), TLS (tls://), or WebSocket (ws://)"
TCPS is the protocol I needed to use to get this to work with our AWS broker.
Hi guys thanks for your positive comments, but I did not have any news from Grafana since 10 months :-(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh oh!
There was an error while loading. Please reload this page.
I required the TLS config to connect to AMAZON. I also wanted to use wildcard subscritions in order to listens to multiple topics in a single subscription.
Tested with AWS IOT core.
I learned GO this morning so I could have done some things stupidly. Coming from the C++, GO looks nice.