ambiser
/
openvidu
mirror of https://github.com/OpenVidu/openvidu.git
8
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
openvidu/openvidu-server/docker/openvidu-health-checker
History
cruizba ddaf34a475 deployment: openvidu_health_check - fix error when 'about:webrtc' page refresh its data 2021-11-05 15:33:46 +01:00
..
Dockerfile deployment: openvidu_health_check - fix error when 'about:webrtc' page refresh its data 2021-11-05 15:33:46 +01:00
README.md Update README.md 2021-11-03 12:09:37 +01:00
create_image.sh deployment: print candidates in openvidu-health-checker docker image test 2021-11-03 20:22:52 +01:00
download_webdrivers.py deployment: openvidu_health_check can test OpenVidu CE/PRO/ENTERPRISE. Cache web drivers in Docker image 2021-11-04 16:47:35 +01:00
entrypoint.sh deployment: openvidu_health_check can test OpenVidu CE/PRO/ENTERPRISE. Cache web drivers in Docker image 2021-11-04 16:47:35 +01:00
openvidu_health_check.py deployment: openvidu_health_check - fix error when 'about:webrtc' page refresh its data 2021-11-05 15:33:46 +01:00
run.sh deployment: openvidu_health_check can test OpenVidu CE/PRO/ENTERPRISE. Cache web drivers in Docker image 2021-11-04 16:47:35 +01:00

README.md

Openvidu health checker

The main purpose of this image is to have a self-contained and indpendent docker image to test and check possible errors in OpenVidu deployments.

This image is also usefull to automation tests of infrastructure.

Current health checks

1. Video working and Turn correctly setup

docker run --shm-size 2g \
    -e OV_URL=<OV_URL> \
    -e OV_SECRET=<OV_SECRET> \
    openvidu/openvidu-health-checker

Just put your OpenVidu url at OV_URL and your OV_SECRET and the stack will be tested.

This health check includes:

    1. Inspector Test Video in Chrome
    1. Inspector Test Video in Firefox
    1. Inspector Test Video in Firefox with TURN forced.

If allways works:

  • STUN/TURN is correctly configured
  • Video Publishing/Subscribing works

If works sometimes:

  • Bad ports opened.
  • Bad internet connection.
  • No possible connection via STUN/TURN

If don't work:

  • Bad port configuration.
  • No possible connection via STUN/TURN
  • Simply a deployment which is not deployed correctly