New Release 4.4.0


Prometheus metrics

zcashd can now be configured to optionally expose an HTTP server that acts as a Prometheus scrape endpoint. The server will reply to GET requests on any request path.

To allow the endpoint, add -prometheusport=<port> to your zcashd configuration (both in zcash.conf or on the command line). After restarting zcashd you may then check the endpoint by querying it with e.g. curl http://127.0.0.1:<port>.

The function contains IP-level entry management guidelines, the default being to permit connections solely from localhost. Users of this function ought to concentrate on the menace from DNS rebinding assaults and never depend on these entry management guidelines for safety. The allowed IPs will be expanded with -metricsallowip=<ip>, which may specify IPs or subnets.

Note that HTTPS shouldn’t be supported, and due to this fact connections to the endpoint usually are not encrypted or authenticated. Access to the endpoint, together with by means of DNS rebinding assaults, must be assumed to compromise the privateness of node operations, by the supplied metrics and/or by timing facet channels and so for now: You ought to NOT use this function whereas personal keys are loaded in zcashd.

The particular metrics names might change in subsequent releases, specifically to enhance interoperability with zebrad.

The submit New Release 4.4.0 appeared first on Electric Coin Company.

You might also like