Hi, appreciate your response and patience. I was quite frustrated last night. Tried to tackle this issue before, without success. 2nd attempt was no more fruitful. LLM are a blessing and a curse, my blood was full boiling last night. I use pro claude, gpt and gemeni and none can seem to handle the entire process.
I am simply trying to send/connect my socket to Grafana. As far as I understand, Grafana has a built in exposed URL, which acts as a live message sub/pub.
I am using latest, v11.
I have ‘enabled’ Grafana Live. (there is no enabled in config, but im getting the console WS request at browser load, which to me confirms Live is enabled)
Ive connected to endpoints like this:
` async with websockets.connect(
'wss://**.fur*.com/api/live/ws',
additional_headers={
'Authorization': 'Bearer glsa_aCI***************_3c1f324d',
}`
Logs, from docker-compose show connection from Service Account User, Auth success, but return server -1 error, or 3501…
WebSocket connection established.
Sending: {"channel": "ds/mydata/temperature", "data": {"streams": [{"labels": "{__name__=\"my_temp\", instance=\"sensor1\"}", "values": [["1741009490746", "88"]]}]}}
Sending: {"channel": "ds/mydata/temperature", "data": {"streams": [{"labels": "{__name__=\"my_temp\", instance=\"sensor1\"}", "values": [["1741009491747", "41"]]}]}}
Connection closed: received 3501 (registered) bad request; then sent 3501 (registered) bad request
(venv) root@ubuntu-s-2vcpu-8gb-amd-nyc2-01:~#
Im behind Nginx, but i think auth success shows this to not be the issue. As far as LLMs say, 3501 is a channel issue. Cannot resolve channel.
I dont kno what the endpoint is, i dont kno if i need a custom backend to define that channel, or if i can just push to a pre-built existing one.
As the user said below, I have the Grafana test data enabled, I have live measurement sample/dummy data being sent correctly. I assumed this is where i would ‘pick up’ my channel being pushed from websocket? I have yet to see anything published.
Aside, I once had the goliath plugin working, a year ago, but with many errors. Now, since i could not solve this Live issue, i reverted to Goliath, and have since discovered more issues. Could not get it working. Logs say it is connecting, but also crashing. Thank you for the Forum Link, it appears they are still supporting. Maybe i will give that another test.
I would love to just use Live. Thanks for listening.
logger=id-service t=2025-03-03T14:25:42.46606392Z level=debug msg="Cached token found" id=service-account:15
logger=context userId=15 orgId=1 uname=***s**1 t=2025-03-03T14:25:42.466356215Z level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=172.18.0.1 time_ms=7 duration=7.196439ms size=0 referer= handler=/api/live/ws status_source=server