...
| Info |
|---|
There may be an issue with the installer and you should also click on the System Metrics check box to ensure all the components are installed. |
| Info |
| Warning |
|---|
You can only expose the metrics to a single metrics database, even if you manually install more than one of the available extensionsinstall a single registry provider, JAMon, Datadog, InfluxDB or Prometheus at a time. If you have previously installed one of the above registries you should remove the corresponding plugin before installing another or the metrics recording will not work. The registry plugins will be named If you do not see the metrics you expect check if there is more than one plugin with that above names. Note that the |
...
Configuration
JAMon
JAMon is an internal metrics database that stores the metrics and makes them available via the existing Weave server status page (under the Timing Summary page). JAMon requires no configuration.
...
The following is a working prometheus.yml configuration file that can be used with a Prometheus server, you just need to change <hostname> to the Weave server hostname and <port> to the port that Weave can be access at. Note you may need to add a change the scheme attribute if you’re not directly accessing Weave over http and are using https.
While this example is enough to get Prometheus working with a Weave server and can serve as a complete Prometheus server configuration file you would likely include more than this, this is intended to just show what is required to add a connection to a Weave server.
...
| Info |
|---|
If you’re going to use a security.xml file from a previous version of Weave it may not include an entry for the Prometheus /metrics endpoint, if this is the case add the following entry to the filterInvocationDefinitionSource property in the filterChainProxy, after PATTERN_TYPE_APACHE_ANT but before /**=httpSessionContextIntegrationFilter,logoutFilter,... |
The default
Other configuration options:
...