Agent Offline Notification
1. Displays "Agent offline for 4 months" indicating the agent has been disconnected for this duration.
2. Notes that the current data is a snapshot from when the agent was last online.
3. Includes a "More Info" link for additional details.
When you get the Agent Offline message at the top of your agent page, Domotz is no longer monitoring your network. Therefore your device statuses are not being updated and cannot be trusted.
Device status of your devices, or any other value you are monitoring, is in their last state before the agent went offline. This means that these values cannot be trusted if the agent is offline:
Device Status and Monitoring with Offline Agent
1. The header indicates "Agent offline for 8 mo," showing the agent's offline duration.
2. The devices are listed under "Industries - Cairo Office" with each device displaying its last known status before the agent went offline.
3. Each device entry shows the connection duration, device ID, location prompt, device type, and IP address.
4. Devices marked with time (e.g., "10 mo") indicate how long they were last active.
5. Devices are no longer monitored once the agent is offline, as indicated in the notes.
6. The list includes various devices like "Raspberry" and "debian11," along with their respective IP addresses and models (e.g., 10.0.2.2).
7. Make note of devices such as the "Unknown" types, which may show only an IP address.
8. The status list helps identify which devices need attention once the agent comes back online.
To see when your agent went offline, navigate under Site Explorer -> YourAgentName -> Network Performance-> Downtime:
Network Performance and Downtime Log
1. Navigate to "Sites Explorer" and select "ACME Inc. Paris Office" to access the "Network Performance" section.
2. Check the status bar at the top indicating that the "Agent" is offline for 4 days.
3. Use the tabs provided to switch between options: "Info," "Route Analysis," "Speed Test," and "Downtime."
4. Review the "How it Works" section under "Downtime" to view connection logs.
5. Note entries such as "Connection Went Down" on January 13 at 5:12 PM CET, highlighted for immediate attention, indicating when an outage occurred.
6. Additional entries show instances of connections going up and down, with corresponding timestamps for analysis.
