> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/ai-agents/hardware-management/device-uptime-monitoring.md).
# Device Uptime Monitoring
Automated monitoring for devices with high uptime (haven't restarted).
The **Device Uptime Monitoring** agent identifies devices that have been running for an extended period without a restart. Long uptime can indicate missing restarts and security updates. You can configure thresholds, notifications, and ticket creation to match your organization's needs - and scope test runs to specific employees for faster validation.
### What it does
* Runs periodic checks for devices with high uptime
* Queries devices that haven't restarted within a threshold
* Marks devices as NEW or existing based on entity tracking
* Sends notifications to device owners about devices that haven't been restarted
* Optionally excludes VIP employees from automated notification delivery
* Generates CSV report with all devices meeting criteria
* Creates ticket with CSV attachment for IT team review (can be toggled off)
### Triggers
**Schedule** - Runs at configured frequency (e.g., daily at 08:00) via cron.
### Approval
No approval required. The agent monitors and alerts, remediation is handled manually or by other workflows.
### Configuration
#### Run Schedule
* **Frequency** - Daily, weekly, monthly, or custom interval
* **Time** - Specific time to run (e.g., 08:00)
* **Timezone** - Timezone for scheduled execution (e.g., UTC+00:00)
#### User Notifications
Toggle to enable/disable notifications to device owners about their devices with high uptime.
* **Exclude VIP employees** - Check this option to prevent VIP employees from receiving automated uptime notifications, keeping sensitive personnel out of automated outreach.
#### Ticket Creation
Enable or disable automatic ticket creation for devices exceeding the uptime threshold. Ticket creation is enabled by default, so existing workflows continue to behave as before with no action required.
* **Create ticket after** - Days without restart before creating a ticket (e.g., 30 days)
When ticket creation is turned off, the downstream steps - CSV report generation and ticket creation - are automatically disabled as well, preventing unnecessary processing.
#### Ticket Destination
* **Desk** - Target desk for created tickets (e.g., IT)
* **Priority** - Priority level for tickets (low, medium, high)
* **Assignee** - Optional assignee for created tickets
#### Test Runs
When triggering a test run, you can provide a target list of employee IDs to scope the check to only those individuals. This lets you validate device uptime monitoring for specific teams, roles, or individuals without running a full-scale check across your entire workforce.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.harmony.io/ai-agents/hardware-management/device-uptime-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.