is this the same as the monitoring part of bbb-exporter?

[mplotsker]

Can it coexist with the full stack monitoring part of https://github.com/greenstatic/bigbluebutton-exporter?

[greenstatic]

Yes, I myself am running such an installation. Both bigbluebutton-monitoring and bigbluebutton-exporter use BBB's API. They do not interfere between each other.

[mplotsker]

what is the url to see that page? your-bbb.com/???? for exporter its your-bbb.com/monitoring thanks

…

On Wed, Dec 9, 2020 at 12:11 PM Gregor Krmelj ***@***.***> wrote: Yes, I myself am running such an installation. Both bigbluebutton-monitoring and bigbluebutton-exporter use BBB's API. They do not interfere between each other. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASB4TAMTTO7KU4OPD66RJ53ST6VSZANCNFSM4UTZD7BA> .

[greenstatic]

bigbluebutton-monitoring is a docker image that hosts the page on port 5000. If you used the provided docker-compose file, you will see that the web server is exposed on the host's networking stack on 127.0.0.1:4000

bigbluebutton-monitoring/docker-compose.yaml

Line 7 in b31a52f

- "127.0.0.1:4000:5000"

You can add this to your nginx config, just like with bigbluebutton-exporter: https://bigbluebutton-exporter.greenstatic.dev/installation/all_in_one_monitoring_stack/#5-configure-nginx

You can use whichever endpoint you would like. Just make sure they don't collide with endpoints BBB uses.
Example:

# Reverse proxy for bigbluebutton-monitoring
location /monitoring2/ {
  proxy_pass http://127.0.0.1:4000/;
  include proxy_params;
}

Feel free to close the issue if you don't have any other questions.

[mplotsker]

this in /etc/bigbluebutton/nginx/monitoring.nginx from exporter # BigBlueButton monitoring location /monitoring/ { proxy_pass http://127.0.0.1:3001/; include proxy_params; what do I add to or replace to make this monitoring work? this? # Reverse proxy for bigbluebutton-monitoring location /monitoring2/ { proxy_pass http://127.0.0.1:4000/; include proxy_params; } what about the 4000:5000 in docker-compose.yaml? do i choose one port or leave both in there? thank you for the the quick responses. Michael

…

On Wed, Dec 9, 2020 at 12:24 PM Gregor Krmelj ***@***.***> wrote: bigbluebutton-monitoring is a docker image that hosts the page on port 5000. If you used the provided docker-compose file, you will see that the web server is exposed on the host's networking stack on 127.0.0.1:4000 https://github.com/greenstatic/bigbluebutton-monitoring/blob/b31a52f3eea81f7227bbaad349a1e5d82b1db265/docker-compose.yaml#L7 You can add this to your nginx config, just like with bigbluebutton-exporter: https://bigbluebutton-exporter.greenstatic.dev/installation/all_in_one_monitoring_stack/#5-configure-nginx You can use whichever endpoint you would like. Just make sure they don't collide with endpoints BBB uses. Example: # Reverse proxy for bigbluebutton-monitoringlocation /monitoring2/ { proxy_pass http://127.0.0.1:4000/; include proxy_params;} Feel free to close the issue if you don't have any other questions. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASB4TANID4ZAC75H23ZIDRTST6XELANCNFSM4UTZD7BA> .

[mplotsker]

should it look like this? # BigBlueButton monitoring location /monitoring/ { proxy_pass http://127.0.0.1:3001/; include proxy_params; } location /monitoring2/ { proxy_pass http://127.0.0.1:4000/; include proxy_params; } or do i include this line somewhere? # Reverse proxy for bigbluebutton-monitoring thanks again Michael On Wed, Dec 9, 2020 at 12:51 PM Michael Plotsker <mplotsker@gmail.com> wrote:

…

this in /etc/bigbluebutton/nginx/monitoring.nginx from exporter # BigBlueButton monitoring location /monitoring/ { proxy_pass http://127.0.0.1:3001/; include proxy_params; what do I add to or replace to make this monitoring work? this? # Reverse proxy for bigbluebutton-monitoring location /monitoring2/ { proxy_pass http://127.0.0.1:4000/; include proxy_params; } what about the 4000:5000 in docker-compose.yaml? do i choose one port or leave both in there? thank you for the the quick responses. Michael On Wed, Dec 9, 2020 at 12:24 PM Gregor Krmelj ***@***.***> wrote: > bigbluebutton-monitoring is a docker image that hosts the page on port > 5000. If you used the provided docker-compose file, you will see that the > web server is exposed on the host's networking stack on 127.0.0.1:4000 > https://github.com/greenstatic/bigbluebutton-monitoring/blob/b31a52f3eea81f7227bbaad349a1e5d82b1db265/docker-compose.yaml#L7 > > You can add this to your nginx config, just like with > bigbluebutton-exporter: > https://bigbluebutton-exporter.greenstatic.dev/installation/all_in_one_monitoring_stack/#5-configure-nginx > > You can use whichever endpoint you would like. Just make sure they don't > collide with endpoints BBB uses. > Example: > > # Reverse proxy for bigbluebutton-monitoringlocation /monitoring2/ { > proxy_pass http://127.0.0.1:4000/; > include proxy_params;} > > Feel free to close the issue if you don't have any other questions. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#7 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ASB4TANID4ZAC75H23ZIDRTST6XELANCNFSM4UTZD7BA> > . >

[greenstatic]

It should be like this:

# BigBlueButton monitoring
location /monitoring/ {
  proxy_pass http://127.0.0.1:3001/;
  include proxy_params;
}

# Reverse proxy for bigbluebutton-monitoring
location /monitoring2/ {
 proxy_pass http://127.0.0.1:4000/;
 include proxy_params;
}

The line 127.0.0.1:4000:5000 means map the socket 127.0.0.1 4000 on the host's networking stack, to port 5000 on the containers networking stack (since the web server in the container, i.e. bigbluebutton-monitoring web server. is listening
on port 5000).

We could have used port 5000 on the host, but didn't because if I recall correctly, it was used by BBB for some service.

[mplotsker]

i think I got it except i do not see any sessions [image: image.png] is there some permissions I need in the docker-compose.yaml or secrets.env file to expose the data? what did I do wrong? thanks michael On Wed, Dec 9, 2020 at 12:57 PM Michael Plotsker <mplotsker@gmail.com> wrote:

…

should it look like this? # BigBlueButton monitoring location /monitoring/ { proxy_pass http://127.0.0.1:3001/; include proxy_params; } location /monitoring2/ { proxy_pass http://127.0.0.1:4000/; include proxy_params; } or do i include this line somewhere? # Reverse proxy for bigbluebutton-monitoring thanks again Michael On Wed, Dec 9, 2020 at 12:51 PM Michael Plotsker ***@***.***> wrote: > this in /etc/bigbluebutton/nginx/monitoring.nginx from exporter > > # BigBlueButton monitoring > location /monitoring/ { > proxy_pass http://127.0.0.1:3001/; > include proxy_params; > > > what do I add to or replace to make this monitoring work? > this? > > # Reverse proxy for bigbluebutton-monitoring > location /monitoring2/ { > proxy_pass http://127.0.0.1:4000/; > include proxy_params; > } > > > what about the 4000:5000 in docker-compose.yaml? do i choose one port or leave both in there? > > > thank you for the the quick responses. > > > Michael > > > > > On Wed, Dec 9, 2020 at 12:24 PM Gregor Krmelj ***@***.***> > wrote: > >> bigbluebutton-monitoring is a docker image that hosts the page on port >> 5000. If you used the provided docker-compose file, you will see that the >> web server is exposed on the host's networking stack on 127.0.0.1:4000 >> https://github.com/greenstatic/bigbluebutton-monitoring/blob/b31a52f3eea81f7227bbaad349a1e5d82b1db265/docker-compose.yaml#L7 >> >> You can add this to your nginx config, just like with >> bigbluebutton-exporter: >> https://bigbluebutton-exporter.greenstatic.dev/installation/all_in_one_monitoring_stack/#5-configure-nginx >> >> You can use whichever endpoint you would like. Just make sure they don't >> collide with endpoints BBB uses. >> Example: >> >> # Reverse proxy for bigbluebutton-monitoringlocation /monitoring2/ { >> proxy_pass http://127.0.0.1:4000/; >> include proxy_params;} >> >> Feel free to close the issue if you don't have any other questions. >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> <#7 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/ASB4TANID4ZAC75H23ZIDRTST6XELANCNFSM4UTZD7BA> >> . >> >

[greenstatic]

The image didn't attach correctly. Try using GitHub's web application and not email reply.

[mplotsker]

[greenstatic]

are you sure you provided the correct API_BASE_URL and API_SECRET?

Check the logs; go to the directory where docker-compose is located and run docker-compose logs -f --tail=100

[mplotsker]

do I need to restart bbb? i restarted nginx but not bbb.

Thanks

[greenstatic]

No, restarting BBB should not be necessary.