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

Export Prometheus monitoring endpoints #337

Closed
michaelfig opened this issue Dec 15, 2019 · 0 comments · Fixed by #338
Closed

Export Prometheus monitoring endpoints #337

michaelfig opened this issue Dec 15, 2019 · 0 comments · Fixed by #338
Labels
deployment Chain deployment mechanism (e.g. testnet)

Comments

@michaelfig
Copy link
Member

Have the deployment mechanism export metrics for the testnet validators as described in https://medium.com/cypher-core/cosmos-how-to-set-up-your-own-network-monitoring-dashboard-fe49c63a8271

This would add new read-only web services on TCP ports 9100 (for host-level monitoring) and 26660 (for tendermint monitoring). To secure them, the validator firewall should at most enable TCP access to these ports by its owner's Prometheus aggregator (which can itself be behind a reverse proxy secured with HTTPS and basic authentication or client certificates).

Of course, if the owner of the validator does not use our deployment mechanism, the default ag-chain-cosmos configuration does not enable these services or expose those ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment Chain deployment mechanism (e.g. testnet)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant