Monitoring

Mividas provides monitoring endpoints for each component, allowing for integration with HTTP monitoring solutions and Syslog to track system health and connectivity.

Mividas Core + Mividas Rooms

• General Status Check: Accessing https://core.example.org/status/ should return a Status 200 when the following services are operational:
  • Database is connected.
  • Background service is active and timely.
  • HTTP service is running.
• HTTP Service Uptime: At https://core.example.org/status/up/, a Status 200 indicates that the HTTP service is up.

Mividas Core – Scheduling API

• Scheduling API: For the Mividas Scheduling API, navigate to https://api.example.org/api/v1/status/up/. A Status 200 here indicates that the API can respond to requests.

Mividas Rooms – Specific Monitoring

• Video Conference System: To check separate FQDN for video conference system answers incoming requests, use https://rooms.example.org/status/up/. A Status 200 confirms that the video conference service is up and reachable.

Mividas Meeting Portal

• Portal General Status Check: The Mividas Meeting Portal can be monitored at https://portal.example.org/status/ where Status 200 means:
  • Database connectivity is functional.
  • HTTP service is accessible.
• HTTP Service Uptime: Confirm HTTP service functionality at https://portal.example.org/status/up/, where Status 200 indicates uptime.

Syslog Configuration

Starting with Mividas Installer v1.8.4, the CLI onboarding wizard enables the configuration of a remote syslog server. For earlier versions, Syslog can be set up manually:

Create Configuration File: Add /etc/rsyslog.d/50-remote.conf with the following parameters based on protocol choice:

UDP:

*.* action(type="omfwd" target="syslog.example.org" port="514" protocol="udp" action.resumeRetryCount="100" queue.type="linkedList" queue.size="10000")

TCP:

*.* action(type="omfwd" target="syslog.example.org" port="514" protocol="tcp" action.resumeRetryCount="100" queue.type="linkedList" queue.size="10000")

TCP+TLS:

global(
    DefaultNetstreamDriver="gtls" 
    DefaultNetstreamDriverCAFile="/etc/ssl/certs/ca-certificates.crt"
)

*.* action(type="omfwd" target="syslog.example.org" port="514" protocol="tls" StreamDriverMode="1" StreamDriverAuthMode="x509/name" action.resumeRetryCount="100" queue.type="linkedList" queue.size="10000")

These configurations ensure that Mividas components are effectively monitored, with syslog capturing essential logs remotely for system health tracking and troubleshooting.