Asset Monitoring lets you track the health of URLs and endpoints that matter to your customers. AgentDesk periodically checks each asset and can automatically create tickets when something goes down.
Adding an asset
- Go to Admin > Portals and open the portal.
- Navigate to the Assets tab.
- Click Add Asset and fill in the details:
| Setting | Description | Constraints |
|---|---|---|
| Name | A label for the asset (for example, "Production API" or "Marketing Site") | Required |
| URL | The endpoint to monitor | Must be a valid URL |
| Description | Optional notes about what this asset is | -- |
| Active | Whether monitoring is enabled | On / Off |
| Check interval | How often to check the asset, in seconds | 5 to 3,600 seconds |
| Timeout | How long to wait for a response before marking the check as failed | 1,000 to 60,000 milliseconds |
| Expected status | The HTTP status code that indicates the asset is healthy (for example, 200) | Any valid HTTP status code |
Asset statuses
Each asset has a current status based on recent check results:
| Status | Meaning |
|---|---|
| Up | The asset responded with the expected status code within the timeout |
| Down | The asset did not respond or returned an unexpected status code |
| Degraded | The asset responded correctly but took longer than 5 seconds |
Failure thresholds
To avoid false alarms from transient issues, you can set an alert after fails threshold. This controls how many consecutive failed checks must occur before an incident is opened and notifications are sent.
For example, setting this to 3 means the asset must fail three checks in a row before it is considered down.
Automatic ticket creation
Enable the auto-create ticket option on an asset to have AgentDesk automatically create a support ticket when the asset goes down. This ensures your team is alerted immediately and can begin investigating without manual intervention.
The ticket includes details about the failure, such as the HTTP status code received and any error message.
Incidents
When an asset goes down (after exceeding the failure threshold), an incident is created.
Incident statuses
| Status | Meaning |
|---|---|
| Open | The asset is currently experiencing an issue |
| Acknowledged | A team member has seen the incident and is investigating |
| Resolved | The asset has recovered and the incident is closed |
Incidents track the started at and resolved at timestamps so you can measure downtime duration.
Status logs
Every health check produces a log entry with the following information:
| Field | Description |
|---|---|
| Response time | How long the asset took to respond, in milliseconds |
| HTTP status | The HTTP status code returned by the asset |
| Error message | If the check failed, a description of what went wrong |
Status logs provide a historical record of asset health. Use them to identify patterns, such as recurring degraded performance at certain times of day.
Manual checks
You can trigger a check at any time by clicking the Check Now button on an asset. This runs an immediate health check outside the regular interval.
API reference
| Method | Endpoint | Description |
|---|---|---|
| GET | /portals/:id/assets | List all assets for a portal |
| POST | /portals/:id/assets | Create a new asset |
| GET | /portals/:id/assets/:assetId | Retrieve a specific asset |
| PUT | /portals/:id/assets/:assetId | Update an asset |
| DELETE | /portals/:id/assets/:assetId | Delete an asset |
| POST | /portals/:id/assets/:assetId/check | Trigger a manual health check |
| GET | /portals/:id/assets/:assetId/logs | Retrieve status logs |
| GET | /portals/:id/assets/:assetId/incidents | Retrieve incidents |