Smarty

  2. Home
  4. Docs
  6. Smarty
  8. Smarty configuration and maintenance
  10. Setting up monitoring and alarms

Setting up monitoring and alarms

Smarty contains built-in tools for monitoring multicast streams and device metrics.

The stream monitoring module allows you to analyze Multicast streams on various parts of the network using a poll of microts agents (analyzers) that are engaged in reading and analyzing streams on the server. Parameters such as bitrate, MPEG-TS structure, CC, PES, PAT errors, synchronization loss, video/sound loss, scrambling are calculated and checked.

The device metrics monitoring and device management module is part of a separate product, MVision, but is configured in a shared Smarty configuration file.

Contents show off

Configuring the Multicast Stream Monitoring Module

In the Smarty configuration file, the following options must be configured:

  • MONITORING_CONCURRENT_STREAMS_COUNT The number of simultaneously polled streams from the analyzers. This parameter affects the performance and speed of updating the data on the stream monitoring page. Data type: int. Default 15.
  • MONITORING_AGENT_SOCKET_TCP_BUFFER The size of the data buffer (in bytes) when receiving a response from the analyzer. Data type: int. By default, 4096.
  • MONITORING_STREAM_CHECKS_TTL_DAYS- the life period (in days) of samples and stream events, after this period the data is automatically deleted. Data type: int. Default 30.
  • MONITORING_STREAM_TEST_DURATION Duration of waiting for a separate stream from the analyzers (in seconds). This parameter affects the performance and speed of updating the data on the stream monitoring page. Default 10.

Example of settings:

MONITORING_CONCURRENT_STREAMS_COUNT = 15
MONITORING_STREAM_TEST_DURATION = 10
MONITORING_AGENT_SOCKET_TCP_BUFFER = 4096
MONITORING_STREAM_CHECKS_TTL_DAYS = 30

Analyst survey takes place on an official team check_streams, detail.

To configure the analyzer on the server, you need to install a microts package (the analyzer itself) and microts_agent (a service that receives requests from Smarty and runs microts processes). These packages are provided as part of Smarty and are available for download in the operator’s personal account.

Adding analyzer servers and threads that need to be analyzed is carried out in the control panel, more about this is described in the relevant documentation section: reference.

Setting up the device monitoring module

MongoDB server is used to store metric data and system information of subscriber devices. This functionality is only available when you install a license for the MVision product.

The minimum version of MongoDB required to work is 3.4.

MongoDB connection settings are set by the following options in the Smarty configuration file:

  • DEVMON_SINGLE_CLIENT - enable the mode of single access monitoring of devices. Provides equal access to both functionality and the entire device monitoring database for all operators in Smarty. In single access mode, each operator can have access to devices that do not belong to the subscribers of this operator. Data type: bool. By default False.
  • MONGODB_MONITORING_HOST - MongoDB server address. Data type: string. By default 127.0.0.1.
  • MONGODB_MONITORING_PORT - MongoDB server port. Data type: int. By default 27017.
  • MONGODB_MONITORING_NAME - the name of the database. Data type: string. By default smarty_device_monitoring.
  • MONGODB_MONITORING_USERNAME User name for authorization. Data type: string.
  • MONGODB_MONITORING_PASSWORD - password for authorization. Data type: string.
  • MONGODB_MONITORING_AUTH_METHOD - authorization method. The authorization method depends on the MongoDB version. Data type: string. By default MONGODB-CR.

In the section INSTALLED_APPS in the Smarty configuration file you need to add a module device_monitoringthen re-migrate the data (command migrate) and restart uwsgi.

Example of settings:

MONGODB_MONITORING_HOST = '127.0.0.1'
MONGODB_MONITORING_PORT = 27017
MONGODB_MONITORING_NAME = 'smarty_device_monitoring'
MONGODB_MONITORING_USERNAME = 'admin'
MONGODB_MONITORING_PASSWORD = 'password'
MONGODB_MONITORING_PUSH_TIMEOUT = 150
MONGODB_MONITORING_VIEW_TIMEOUT = 600,000
MONGODB_MONITORING_AUTH_METHOD = 'MONGODB-CR'

INSTALLED_APPS +=
'device_monitoring',
)

Alerming tuning

Adding triggers and contacts to send alerts is described in the relevant documentation section: reference.

To work alarm, you also need to configure the sending of Email: reference.