The Agents screen is accessible by logging into the Web Console and navigating to [Manage→DPOD Health→Agents].
DPOD agents are responsible for collecting data (either actively or passively) from monitored devices and storing it in the Big Data the Store. This screen allows you to verify that the agents are up and running.
...
The Agent Status section of the screen is a set of 3 widgets, each displaying data related to a different set of DPOD Agents: Syslog, WS-M and Resources. The agents are monitored internally by a KeepAlive service. For a list of all system services, and an explanation on KeepAlive processing, see section on System Services Management.
Each collector agent is displayed in a colored box (see below). Click an agent's name to open its details in the Agent's Detail view.
...
| Detail | Description | Desired State |
|---|---|---|
| General Health Status | The general health status of the agent is relayed by the color of the box wrapping its details.
Possible agent issues :
| Green - the agent is healthy. |
| Date / Time | The timestamp of the last successful record processed by the agent (Syslog record or Keepalive check). A delay of over a minute may suggest a performance problem. Note: It is important to verify that system time is time synced correctly when reading these values. | < 3 minutes |
| Msg. Rate | This is the total number of messages of all types (syslog, WS-M, and keepalive messages) processed by this agent in the last 10 minutes. Verify:
You may redirect syslog traffic from one agent to another by assigning it to a domain a specific agent. For more details see Adding Monitored DevicesGateways. | 1 < value < 500,000 (if there are any monitored devices) |
| Dropped Msgs (For Syslog and WS-M agents) | This is the total number of syslog or WS-M messages that were sent from the monitored devices but were not processed by the DPOD agent in the last 10 minutes. Dropped messages usually indicate that the agent cannot keep up with the load, consider redistribution of traffic to other agents. | 0 |
If you encounter any problems, see how to Troubleshoot & Support links to agent status troubleshooting.
...
| Graph | Details | Desired State |
|---|---|---|
| Files Process Pending | The graph depicts the number of large payloads waiting to be processed. A value higher than 1000 indicates a high load on WS-M subscription. WS-M usage should be avoided until this folder is cleared by the system or you clear it manually. | Only a few files displayed |
Channel Utilization | The graph depicts stream processing usage in percentage. Each colored graph denotes a different agent. Verify that all agents use less than 80% of their stream processing capacity. If usage goes above 80%, data coming in from collector agents might be lost. | Under 80% for all agents |
Agents Free Memory | The graph depicts the collector agents’ free memory over time, where each agent is denoted in a different color. When an agent's free memory is too low, you might encounter performance problems. See how to Troubleshoot & Support the issue. | Verify that each agent |
...
| Column | Description |
|---|---|
| Device | The device emitting the message. Click on the device name to view the device in the Raw Messages Logs view. |
| Domain | The domain for this message |
| Category | Always montier-ka |
| Severity | Always debug |
| Time | Timestamp for the Keep-Alive message |
| Direction | N/A |
| Object Type | N/A |
| Object Name | N/A |
| Trans. ID | N/A |
| Client IP | This will always be the originating host so 0.0.0.0 |
| Message | Keep-Alive message text. |
...
| Graph | Description | ||
|---|---|---|---|
| Message Rate (per sec) | This widget displays a graph of the number of messages per second going through this agent over the last 24 hours period | ||
| Dropped Syslog Messages | This graph shows the number of messages dropped by the agent.
| ||
| Channels Utilization | The graph depicts stream processing usage of the current agent in percentage. | ||
| Free Memory | The graph depicts the collector agent free memory over time. |
...