Inventory Device Log
Endpoints Summary
GET
/inventory_device_log/
Swagger ↗
GET
/inventory_device_log/{id}/
Swagger ↗
The Inventory Device Log API provides comprehensive access to device operation
logslogs, settings changes, andsettingscommandhistoryexecutionwithin the Zequenze Control platform.history. These endpoints allow you toretrievetrackdetailed logs ofall deviceactions,interactions,parametermonitorchanges,pendingcommands, events,operations, andalerts with comprehensive filtering capabilities. Use these endpoints to monitor device operations, troubleshoot issues, and trackaudit configuration changesoveracrosstime.your device inventory.
Base URL: https://control.zequenze.com/api/v1
Authentication: All endpoints require a Bearer token:
Authorization: Bearer <your-api-token>
Overview
The Inventory Device Log API provides comprehensive access to device operational logs and settings history. This API is essential for monitoring and auditing device behavior,operations trackingwithin your network infrastructure. These endpoints provide detailed logging capabilities that track every interaction between your management system and devices, including configuration changes, command executions, alerts, and troubleshootingoperational device issues in managed network environments.events.
Key Features:
-
ActionComprehensiveTrackingLogging:MonitorTrack all deviceactionsoperations includingset/getsettingsoperations,changes, commands, events, and alerts -
Parameter Management: Track parameter value changes and configuration updates
Common Scenarios:Use Cases:
Audit trails forTroubleshooting device configuration issues by reviewing recent changes
The API uses cursor-based pagination for efficient data retrieval and supports extensivecomprehensive filtering options to help you find specific log entries quickly.
Endpoints
GET /inventory_device_log/
Description: Retrieves a paginated list of device operation logs with comprehensive filtering options.capabilities. This endpoint is your primary toolessential for accessingmonitoring device operationalactivities, history,tracking including parameterconfiguration changes, commands, events, and alerts. Use the various filter parameters to narrow down results to specific devices, time periods, actions, oranalyzing operational states.patterns across your device inventory.
Use Cases:
- Monitor recent device
activityactivities and configuration changes
Full URL Example:
https://control.zequenze.com/api/v1/inventory_device_log/?parent__id=123&action=sv&datetime__gte=2024-01-01&action=sv&is_pending=false&limit=50
Parameters:
| Parameter | Type | In | Required | Description |
|---|---|---|---|---|
| datetime__gte | string | query | No | Filter logs from this date/time onwards. 2024-01-01, 2024-01-01 10:30:00, or 2024-01-01T10:30:00+00:00 |
| datetime__lte | string | query | No | Filter logs up to this date/time. 2024-01-, 2024-01-, or 2024-01- |
| parent__id | string | query | No | Filter logs |
| action | string | query | No | Filter by action type: sv (Set), uv (Unset), gv (Get), sa (Set attribute), cr (Create), de (Delete), cm (Command), ev (Event), er (Error), ar (Alert raised), ac (Alert cleared) |
| is_pending | boolean | query | No | Filter |
| is_applied | boolean | query | No | Filter |
cURL Example:
curl -X GET "https://control.zequenze.com/api/v1/inventory_device_log/?parent__id=123&action=sv&datetime__gte=2024-01-01&action=sv&limit=20"50" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Example Response:
{
"next": "https://control.zequenze.com/api/v1/inventory_device_log/?cursor=eyJjcmVhdGVkIjoiMjAyNC0wMS0xNVQxMDozMDowMFoifQ%3D%cD0yMDI0LTA0LTI0KzAwJTNBMDA%3D",
"previous": null,
"results": [
{
"id": 1247,1001,
"created": "2024-01-15T10:15T14:30:00Z",
"last_change": "2024-01-15T10:15T14:30:15Z",
"user": 42,5,
"parent": 156,123,
"type": "string",
"action": "sv",
"command": "Reconf",
"name": "WiFi Configuration Update",
"variable_name": "Device.WiFi.SSID.1.SSID",
"value": "Corporate_Network_5G"CorporateNetwork_2024",
"is_pending": false,
"is_applied": true,
"status": 200,
"message": "ParameterConfiguration updatedapplied successfully"
},
{
"id": 1246,1002,
"created": "2024-01-15T09:15:15T14:25:00Z",
"last_change": "2024-01-15T09:15:15T14:25:30Z",
"user": 38,3,
"parent": 156,124,
"type": "boolean",
"action": "sv"cm",
"command": null,"Reboot",
"name": "EnableScheduled Auto-Update"Device Reboot",
"variable_name": null,
"value": null,
"is_pending": true,
"is_applied": false,
"status": 100,
"message": "Reboot command sent to device"
},
{
"id": 1003,
"created": "2024-01-15T14:20:00Z",
"last_change": "2024-01-15T14:20:05Z",
"user": null,
"parent": 125,
"type": null,
"action": "ar",
"command": "Parameter Threshold",
"name": "High CPU Usage Alert",
"variable_name": "Device.ManagementServer.AutoUpdate.Enabled"DeviceInfo.ProcessStatus.Process.1.CPUUsage",
"value": "true"89.5",
"is_pending": false,
"is_applied": true,
"status": 200,
"message": "Auto-updateCPU enabledusage successfully"exceeded },threshold {of 80%"id": 1245,
"created": "2024-01-15T08:45:00Z",
"last_change": "2024-01-15T08:45:00Z",
"user": null,
"parent": 203,
"type": null,
"action": "ev",
"command": "Boot",
"name": "Device Boot Event",
"variable_name": null,
"value": null,
"is_pending": false,
"is_applied": true,
"status": 200,
"message": "Device completed boot sequence"
}
]
}
Response Codes:
| Status | Description |
|---|---|
| 200 | Success - Returns paginated list of device logs |
GET /inventory_device_log/{id}/
Description: Retrieves detailed information forabout a specific device log entry by its unique identifier.entry. This endpoint provides complete details about a single device operation, including parameter changes, command execution results,status, timestamps, and operationalany status.error Use this when you need comprehensive information about a specific log entry identified from the list endpoint.messages.
Use Cases:
- Get
completedetaileddetailsinformation about a specific device operation - Investigate failed operations and error messages
Full URL Example:
https://control.zequenze.com/api/v1/inventory_device_log/1247/1001/
Parameters:
| Parameter | Type | In | Required | Description |
|---|---|---|---|---|
| id | integer | path | Yes | Unique identifier of the device log entry |
| datetime__gte | string | query | No | Additional filter |
| datetime__lte | string | query | No | Additional filter |
| parent__id | string | query | No | Additional filter by device ID |
| variable_name | string | query | No | Additional filter by variable name |
| action | string | query | No | Additional filter by action type |
| is_pending | boolean | query | No | Additional filter by pending status |
| is_applied | boolean | query | No | Additional filter by applied status |
cURL Example:
curl -X GET "https://control.zequenze.com/api/v1/inventory_device_log/1247/1001/" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json"
Example Response:
{
"id": 1247,1001,
"created": "2024-01-15T10:15T14:30:00Z",
"last_change": "2024-01-15T10:15T14:30:15Z",
"user": 42,5,
"parent": 156,123,
"type": "string",
"action": "sv",
"command": "Reconf",
"name": "WiFi Configuration Update",
"variable_name": "Device.WiFi.SSID.1.SSID",
"value": "Corporate_Network_5G"CorporateNetwork_2024",
"is_pending": false,
"is_applied": true,
"status": 200,
"message": "ParameterConfiguration updatedapplied successfully"
}
Response Codes:
| Status | Description |
|---|---|
| 200 | Success - Returns |
| 401 | Unauthorized - Invalid or missing |
| 403 | Forbidden - Insufficient permissions to access this log entry |
| 404 | Not Found - Log entry with specified ID does not exist |
Data Models
Device Log Entry Fields
Action Codes
Status Codes
Common Use Cases
Use Case 1: Monitor Recent Device Configuration ChangesActivities
Track all parameterrecent changesoperations madeacross devices to devicesmaintain inoperational awareness.
# Get logs from the last 24 hours
tocurl ensure-X configurationGET compliance and detect unauthorized modifications.
# Get all parameter set operations from yesterday
"https://control.zequenze.com/api/v1/inventory_device_log/?datetime__gte=2024-01-1415T00:00:00Z&action=sv&is_applied=truelimit=100" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Use Case 2: Troubleshoot Failed Device Operations
Identify and analyze failed operations by filtering for error statuses and pendinginvestigate operations that haven'tfailed completedor successfully.are stuck in pending status.
# Find all failed operations with error (status >= 400)
curl -X GET "https://control.zequenze.com/api/v1/inventory_device_log/?status=500&is_applied=false&datetime__gte=2024-01-15" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Use Case 3: Audit Device Alert Activity
Monitor alert patterns by tracking alert raised and cleared events across devices to identify recurring issues or maintenance needs.
# Get all alert-related events from the past week
https://control.zequenze.com/api/v1/inventory_device_log/?datetime__gte=2024-01-08&action=ar,ac
Use Case 4: Track Specific ParameterConfiguration Changes
MonitorGenerate reports of all configuration changes to critical device parameters like WiFi settings, security configurations, or network parameters across your device inventory.
# Monitor WiFi SSID changes across all devices
https://control.zequenze.com/api/v1/inventory_device_log/?variable_name=Device.WiFi.SSID.1.SSID&action=sv
Use Case 5: Generate Device Activity Reports
Create comprehensive activity reports for specific devices by combining device filtering with time-based queries for audit and compliance purposes.
# Get all activityconfiguration changes (set/unset actions)
curl -X GET "https://control.zequenze.com/api/v1/inventory_device_log/?action=sv&datetime__gte=2024-01-01&datetime__lte=2024-01-31" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Use Case 4: Monitor Device Alerts
Track alert patterns and frequencies across your device fleet.
# Get all raised alerts in the last week
curl -X GET "https://control.zequenze.com/api/v1/inventory_device_log/?action=ar&datetime__gte=2024-01-08" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Use Case 5: Track Specific Device History
Review complete operational history for a specific device.
# Get all logs for device ID 156123
incurl January-X 2024GET "https://control.zequenze.com/api/v1/inventory_device_log/?parent__id=156123&datetime__gte=2024-01-01&datetime__lte=2024-01-31limit=500" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Response Field Reference
Action Types
Status Codes
Parameter Types
Common parameter types you'll encounter in device logs include string, integer, boolean, datetime, select, and specialized types like password and deviceDash for dashboard configurations.
Best Practices
Efficient Filtering:
Use Date Filtering:Alwaysapplyuse date ranges (datetime__gteanddatetime__lte) when possible to limit result sets
parent__id) when investigating device-specific issues
Use action filters to focus on specific types of operations
Pagination Management:
limit values based on your use case (default: 100, max: 1000)
Use cursor-based pagination for consistent results when data is being updated
Store pagination cursors temporarily if you need to Performance Optimization:
is_pending=trueImplement Error HandlingHandling::
status field cursorlimitparent__idvariable_nameactionmessage fields for detailed error information
Monitor is_pending and is_applied flags for operation status
Security Considerations:
Monitoring and Alerting: