THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
See: /openmeetings-web/src/main/webapp/WEB-INF/web.xml#L110
View your metrics in Prometheus
Above will enable an endpoint to publish the metrics as HTTP endpoint. You can then use Prometheus (or other tools) to read it in and graph it.
Easiest is to point to it via a Prometheus that runs in a docker container. How to startup the docker container:
| Code Block |
|---|
docker run --rm -it -p 9090:9090 -v /Users/Sebastian.wagner/Documents/mywork/openmeetings/_REPO/copy-files/
:/etc/prometheus/prometheus.yml prom/prometheus |
Example local-prometheus.yml file to reference in above docker command (points to local running OpenMeetings instance)
| Code Block | ||||
|---|---|---|---|---|
| ||||
global:
scrape_interval: 15s # By default, scrape targets every 15 seconds.
evaluation_interval: 15s # Evaluate rules every 15 seconds.
# Attach these extra labels to all timeseries collected by this Prometheus instance.
external_labels:
monitor: 'scalyr-blog'
rule_files:
- 'prometheus.rules.yml'
scrape_configs:
- job_name: 'prometheus'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
static_configs:
- targets: ['localhost:9090']
- job_name: 'openmeetings-local'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
metrics_path: 'openmeetings/services/metrics/'
static_configs:
- targets: ['192.168.1.66:5080']
labels:
group: 'production'
|
Change 192.168.1.66:5080 to your local running OpenMeetings instance. Below graphs and queries are done using this docker container.
What kind of metrics are we collecting
...