...
These tools provide basic graphing, but are primarily for collecting the metrics over a long period; another tool would be used to display and monitor that information, for example Grafana https://grafana.com/. A basic dashboard for Grafana that uses Prometheus is available for import to Grafana from here.
Short Term Monitoring
JAMon does short term monitoring but not monitoring of your system over the long term. The monitoring is described as short term because once the Weave services are restarted, the metrics will be lost as they are cleared after a restart.
...
Out of the box, the Prometheus database requires no configuration to start it working, and it then presents the available metrics for collection from the /weave/metrics URL. To utilise the metrics you need to point your Prometheus server to access that URL to periodically collect the metrics from the Weave server.
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 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.
| Code Block | ||
|---|---|---|
| ||
scrape_configs:
- job_name: 'weave'
scrape_interval: 1m
metrics_path: '/weave/metrics'
static_configs:
- targets:
- <hostname>:<port> |
| 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,... |
...