This document describes how to identify and respond to resource incidents in Orbit Server Manager on the Segura® Platform.
Requirements
- Access to Orbit Server Manager.
- Permission to view and monitor incidents in Orbit.
Step 1: Access the incident panel
- On the Segura® Platform, in the navigation bar, hover over the Products menu and select Orbit Server Manager.
- In the home page, click Incident.
- Locate the incident related to resources or connectivity.
Step 2: Identify the incident type
Review the incident description to identify which condition was detected by the system.
Incidents may be related to:
- Appliance minimum resources;
- Available disk space;
- Communication ports between nodes in a cluster environment;
- Service ports in a standalone environment.
Step 3: Take the recommended action
Based on the incident type, take the corresponding action.
Appliance minimum resources
If the incident indicates CPU, RAM, or total disk space below the recommended level:
- Validate the current instance configuration;
- Adjust the infrastructure resources as needed;
- Wait for the next automatic system check.
Available disk space
If the incident indicates critical space on the recording partition:
- Perform data cleanup, if applicable;
- Increase the instance disk space;
- Confirm that the available space returned to the expected level.
When the available space on the recording partition falls below 10 GB, the start of new remote sessions is automatically blocked.
Communication ports between nodes
If the incident indicates port failures in a cluster environment:
- Validate the connectivity between the nodes;
- Review firewall rules and network configuration;
- Confirm that the documented cluster communication ports are responding.
Service ports in a standalone environment
If the incident indicates a failure in a local service port:
- Check whether the corresponding service is running;
- Review firewall, network, and load balancing rules, if applicable;
- Confirm that the port is responding correctly again.
Step 4: Confirm normalization
- Monitor the incident in the Orbit panel.
- Wait for the next automatic check.
- Confirm that the incident was closed automatically after the resource or connectivity condition returned to normal.
Resource and connectivity incidents are closed automatically when the monitored condition returns to the expected state.
Step 5: Verify notifications
Confirm that notifications were received through the configured channels:
- Orbit incident panel;
- Instance administrator email;
- SIEM via syslog.
For email notifications to be sent correctly, configure the notification email in Orbit Server Manager > Settings > Application.
Verify your results
After completing the steps above, check the following points:
- The incident must correctly reflect the affected resource or service;
- The condition must be normalized with the applied action;
- The incident must be closed automatically after the next successful check.