From 878e1aee36faff91bc60b54c886561b94fe33dfd Mon Sep 17 00:00:00 2001 From: anmg Date: Fri, 25 Sep 2020 13:26:11 +0300 Subject: [PATCH 1/3] Panel Recordings Unprocessed - name correction --- extras/dashboards/all_servers.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extras/dashboards/all_servers.json b/extras/dashboards/all_servers.json index acd98ac..4d02574 100644 --- a/extras/dashboards/all_servers.json +++ b/extras/dashboards/all_servers.json @@ -1203,7 +1203,7 @@ ], "timeFrom": null, "timeShift": null, - "title": "Recordings Processing", + "title": "Recordings Unprocessed", "type": "gauge" }, { From da83b45d0d4e13b90fd6ea61f3bc78099f4d6431 Mon Sep 17 00:00:00 2001 From: anmg Date: Fri, 25 Sep 2020 13:35:35 +0300 Subject: [PATCH 2/3] Change Nginx config location --- docs/installation/all_in_one_monitoring_stack.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/installation/all_in_one_monitoring_stack.md b/docs/installation/all_in_one_monitoring_stack.md index 5077ab3..ec05420 100644 --- a/docs/installation/all_in_one_monitoring_stack.md +++ b/docs/installation/all_in_one_monitoring_stack.md @@ -71,8 +71,7 @@ sudo docker-compose up -d ``` ### 5. Configure Nginx -Add the location directive to your Nginx web server (`/etc/nginx/sites-available/bigbluebutton`) that will proxy traffic to -`127.0.0.1:3001`. +Add the location directive monitoring.nginx to your Nginx web server (`/etc/bigbluebutton/nginx/monitoring.nginx` - config from this location will be loaded automatically by nginx BigBlueButton config) that will proxy traffic to `127.0.0.1:3001`. ```text # BigBlueButton monitoring @@ -98,9 +97,7 @@ location /monitoring/ { variable as well. !!! Tip - When upgrading BigBlueButton, the upgrade procedure will overwrite the contents of `/etc/nginx/sites-available/bigbluebutton` - thereby causing you to lose access to your metrics. - So after the upgrade to BigBlueButton you will need to add the location directive again. + When upgrading BigBlueButton, the upgrade procedure will not overwrite the contents of `/etc/bigbluebutton/nginx/`folder. You could also add a separate site configuration, but this will require you to point another domain to the server to do virtual hosting and acquire a separate HTTPS certificate. From b71b0cec19d226eb6ebb735bbe7dbbac68a53ce2 Mon Sep 17 00:00:00 2001 From: anmg Date: Fri, 25 Sep 2020 22:13:09 +0300 Subject: [PATCH 3/3] Nginx config correct place --- docs/installation/bigbluebutton_exporter.md | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/installation/bigbluebutton_exporter.md b/docs/installation/bigbluebutton_exporter.md index d7f8624..5852f65 100644 --- a/docs/installation/bigbluebutton_exporter.md +++ b/docs/installation/bigbluebutton_exporter.md @@ -89,8 +89,8 @@ sudo htpasswd -c /etc/nginx/.htpasswd metrics If you already have `/etc/nginx/.htpasswd` file then do not add the `-c` flag, otherwise you will overwrite the file. ### 6. Add Nginx site configuration -Add the location directive to your Nginx web server (`/etc/nginx/sites-available/bigbluebutton`) that will proxy traffic to -`127.0.0.1:9688`. +Add the location directive to your Nginx web server (`/etc/bigbluebutton/nginx/metrics.nginx` - BigBlueButton Nginx config will load config from location `/etc/bigbluebutton/nginx/*.nginx`) that will proxy traffic to +`127.0.0.1:9688`. ```text # BigBlueButton Exporter (metrics) @@ -104,10 +104,6 @@ location /metrics/ { ``` !!! Tip - When upgrading BigBlueButton (using the script), the upgrade procedure will overwrite the contents of `/etc/nginx/sites-available/bigbluebutton` - thereby causing you to lose access to your metrics. - So after the upgrade you will need to add the location directive again. - You could also add a separate site configuration, but this will require you to point another domain to the server, configure virtual hosting and acquire a separate HTTPS certificate.