https://github.com/vmarchaud/consul-topology-visualizer

Visualize latency between your Consul nodes
https://github.com/vmarchaud/consul-topology-visualizer

consul latency monitoring vizualisation

Last synced: 14 days ago
JSON representation

Visualize latency between your Consul nodes

• Host: GitHub
• URL: https://github.com/vmarchaud/consul-topology-visualizer
• Owner: vmarchaud
• License: mit
• Created: 2018-12-20T21:13:27.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2019-12-12T10:41:14.000Z (almost 5 years ago)
• Last Synced: 2024-08-01T06:21:08.283Z (3 months ago)
• Topics: consul, latency, monitoring, vizualisation
• Language: JavaScript
• Homepage:
• Size: 35.2 KB
• Stars: 20
• Watchers: 3
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

• awesome-consul - consul-topology-visualizer: Visualize latency between your Consul nodes

README

        
# Consul Topology

This tool is made to vizualise latency between consul nodes based on the [Coordinate API](https://www.consul.io/docs/internals/coordinates.html) to compute the data.

![](https://i.imgur.com/j6v0iep.png)

## Inspiration

Some people might recognize the similarity with [Goldpinger](https://github.com/bloomberg/goldpinger) which is indeed the tool that i used to kickstart my version, so big thanks you to them for open sourcing this tool in the first place.

The first difference is that i only wanted to vizualise things and didn't want to actually get alerted nor get metrics from this tools. But it's pretty trivial so someone need it, just ask and i might add it.

The second difference is that we don't actually need to deploy anything in your infrastructure since Consul compute pretty much all the data for us.

## Configuration

As said earlier, you don't need to deploy anything along side your infrastructure, but there are still some configuration :

- `CONSUL_HTTP_ADDR`: The address of the consul endpoint (can be either a master or client)

- `CONSUL_CACERT`: The **path** (on the FS) to the Consul CA cert

- `CONSUL_CLIENT_CERT`: The **path** (on the FS) to the client cert

- `CONSUL_CLIENT_KEY`: The **path** (on the FS) to the client private key

Of course if you can access Consul in HTTP, you don't need to configure the certificate.

Note: It's the same environment variables as the CLI so it avoid you re-configured them on your laptop if you already have the CLI :)

## Notes

I hacked this quickly during the holiday so it might not be the state of the art UX or code. Feel free to make a PR to implement the things that you want.

I've built an image for deployment it into my production environment so if you want to re-use it: https://cloud.docker.com/repository/docker/vmarchaud/consul-topology

## More screenshots

- https://i.imgur.com/j6v0iep.png

- https://i.imgur.com/pML1dIH.png