Can't add datasource - Bad Request[Q]

[Memorist23]

Hi there
I've just added go-carbon on my grafana server but i can't seen to add it as a data source.
I'm getting a HTTP error Bad Gateway.
After further investigation it looks like go-carbon is listening on ipv6:2003
We don't use ipv6 and i can't seem to change it. I've disabled IPv6 on my debian server, restarted not change.
I've change the the config to with now change.
Any ideas how to fix?

[udp]
listen = "127.0.0.1:2003"
enabled = true
buffer-size = 0

[tcp]
listen = "127.0.0.1:2003"
enabled = true
buffer-size = 0
compression = ""

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      394/nginx: master p 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      401/sshd            
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN      399/postgres        
tcp        0      0 127.0.0.1:7002          0.0.0.0:*               LISTEN      463/go-carbon       
tcp        0      0 127.0.0.1:7003          0.0.0.0:*               LISTEN      463/go-carbon       
tcp6       0      0 :::2003                 :::*                    LISTEN      463/go-carbon       
tcp6       0      0 :::2004                 :::*                    LISTEN      463/go-carbon       
tcp6       0      0 :::22                   :::*                    LISTEN      401/sshd            
tcp6       0      0 :::3000                 :::*                    LISTEN      420/grafana-server  
udp        0      0 0.0.0.0:68              0.0.0.0:*                           309/dhclient        
udp6       0      0 :::2003                 :::*                                463/go-carbon   

[bom-d-van]

hi, we usually don't have go-carbon as a direct grafana datasource. you would need to deploy carbonapi with go-carbon as backend and make carbonapi as a data source in grafana.

[Civil]

To be precise you can use:

1. graphite-web on top (on the same server for example) and connect graphite-web via carbonlink to go-carbon (that would have a tags support)
2. graphite-web, but use RemoteFinder and it's CLUSTER_SERVERS configuration option and point it to a carbonserver (component of go-carbon) address (it doesn't seems that you have it enabled, unless that's oone of the 7002-7003 port listener). That way you can have it on different servers (or in different conatiners) but you'll loose tags support
3. Use carbonapi (either go-graphite's or booking's) to talk to carbonserver component mentioned above. That would be the fastest way (carbonapi is much faster than graphite-web), but again, no tags support at this moment.

I'm also not sure if there are other projects that can talk to graphite's CLUSTER_SERVER compatible backend, I guess there are, so instead of graphite-web in setup in point 2 you can use other software (maybe metrictank can, but I'm not sure).

Listeners that you've mentioned in your comment, are for input only, so you can send graphite line protocol messages over TCP or UDP to port 2003 (localhost) and go-carbon will start writing that data to whisper files on disk.

[Memorist23]

Thanks all, I didn't realize I needed it with carbonapi. I don't think i need the tagging.
Just using it for rlm license reporting.