How to configure the monitoring

In this documentation we will only describe the hardware, operating system and monitoring services that can be queried through the SNMP protocol and the Zabbix agent. In addition to SYSLOG messages that can be forwarded to SIEM systems and notification emails triggered by Orbit.

Monitoring through Zabbix

By default, the Zabbix Agent service will be inactive on the instance. To activate it, access the menu Orbit Config Manager > Server > Services, locate the Zabbix Agent service and click on the Start action.

To configure the Zabbix Server that will receive the data:

1. Go to menu Orbit Config Manager > Settings > Application.
2. Fill in the Server IP and Server Connection Port fields with the destination server data
3. If you want, you can add up to 3 servers, just fill in the server IP and the connection port to the server.
4. Fill in the Listen IP field with the instance access interface IP.
5. Finally, keep Listen Port with port 10050.

Monitoring through SNMP

The instance has support for SNMPv2 and from version 3.8 there is support for SNMPv3 configured only by Orbit Command Line. See the Orbit Command Line documentation for more details.

Through the Orbit Web interface, it is possible to configure the servers allowed to read and the community, through the menu Orbit Config Manager > Server > Settings.

Monitoring through SYSLOG (SIEM)

The senhasegura is compatible with the most used SIEM tools in the market and offers support for the transmission of messages in CEF, Syslog (RFC 5424), and Sensage formats.

To configure access the menu Orbit Config Manager > Settings > Application > Syslog configuration and fill the following fields:

• Message format: Refers to the selected format of the message to be sent, which can be CEF, Syslog (RFC 5424), or Sensage.
• Notification plugin: Used only in cases of paid customization projects. Keep this field at its default value. It is not recommended to manipulate this control without the supervision of the Support team.
• Message sending protocol: Choose between TCP or UDP.
• Network Connector: Refers to the network connector to send the message.
• Use network connector: Indicates if the network connector selected will be utilized in the Syslog message-sending configuration.

• Servers for message sending: A list of IPv4 servers, separated by commas, that will receive the messages.

Orbit alerts and incidents

Some alerts are specific to modules and features of senhasegura . These alerts are monitored by Orbit and forwarded to certain users depending on their criticality.

To configure the recipients to receive these alerts, go to the menu Orbit Config Manager > Settings > Applications and add the emails in the field Notification e-mail. The pending solution incidents will be presented in the menu Orbit Config Manager > Application > Incidents.

Application activation

The activation key is required to use the application. The access to your application will be blocked in DAYS.

Priority

LOG_ALERT

Resolution

• Get in touch with our support team to renew your application license.

Mysql Service

Mysql service failed: MESSAGE

Priority

LOG_ALERT

Resolution

• If you are running a senhasegura cluster environment, first at all assume the next node as Primary.
• If you are running into a DR schema, enable the DR instance as primary.
• After normalize the environment, isolate the problematic instance and start a database recovery mirroring the new primary instance.

DB Cluster

Database Cluster failed: MESSAGE

Priority

LOG_ALERT

Resolution

• First at all assume the next node as Primary.
• After normalize the environment, isolate the problematic instance and start a database recovery mirroring the new primary instance.

Cluster Replication Health

The node cannot apply write-sets as quickly as it receives them: AVGVALUE
The node flow control was paused to a long time: FLOWCONTROLVALUE
Replication throttling or network throughput issues: AVGQUEUE_VALUE

Priority

LOG_ERR

Resolution

• Network latency should be configured. At the Orbit cluster configuration set that nodes are in different data centers.

Cluster Replication Issues

Node is not synced: STATUS

Priority

LOG_ERR

Resolution

• Checkup if the node can reach the others cluster members and reconfigure the problematic node.

Database Primary key increase alert

Database Primary key increase alert: Table TABLE_NAME

Priority

LOG_ALERT

Resolution

• Execute the Primary key maintenance procedure located at senhasegura PAM Solution.

Remote partition problem

Your remote partition has a problem! Please check your mounted partitions.

Priority

LOG_ALERT

Resolution

• Check if the target device can be reached by the senhasegura instance.
• Check if the credential used to authenticate is enabled and has the right permission to access the device.
• Check if the target device support the configured protocol.

Inodes usage

Inodes block usage problem: DETAIL

Priority

LOG_ALERT

Resolution

• Execute the INODE maintenance procedure located at senhasegura PAM Solution.

Disk Usage

Disk space usage problem: DETAILS

Priority

LOG_ALERT

Resolution

• Attach a new virtual disk to the instance and execute the partition resizing.

Files Replication

Replication interval is too long! Last sync: TIME
Replication error! Pack: ID

Priority

LOG_ALERT

Resolution

• Session files replication failure. Execute the rsync manually as described at Force files resync procedure at senhasegura PAM Solution.

Application version

Application version is different between nodes: DETAILS

Priority

LOG_ALERT

Resolution

• Execute orbit upgrade into all instances.

System restart required

One or more processes require a full reboot.

Priority

LOG_ALERT

Resolution

• Execute the system reboot. Into a cluster environment you should reboot one instance by time given the right time to the cluster identify every cluster leave and entrance.

Master key not set

Master key not set. It is not possible to create a backup of your credentials.

Priority

LOG_ALERT

Resolution

• Perform the Master Key ceremony.

Master key guardian inactive

Master key guardian inactive. You have inactive guardians in the system, redo the master key process.

Priority

LOG_ALERT

Resolution

• Check if the guardian made wrong its login and disabled its user. If it is not the case, redo the master key process.

Proxy Service alert

Proxy Service not running: DETAILS

Priority

LOG_ALERT

Resolution

• Restart the service using orbit service command. If the problem continue, restart the instance.

Default E-mail Account

E-mail Account is not set up

Priority

LOG_ERR

Resolution

• Register an SMTP account.

System without initial key settings

System without initial key settings. Run the system setup wizard to resolve this issue.

Priority

LOG_ALERT

Resolution

• This error should appears only into not configured instances. Execute the deployment steps to solve the incident.

System key is missing or corrupted

System key is missing or corrupted. Contact system administrator immediately.

Priority

LOG_ALERT

Resolution

• The system key, generated into deployment stage, is not found. It can occurs when an really old backup is restored with an updated senhasegura software. Call our support team.