Support Required for Nx Status Monitoring
AnsweredWe are integrating Nx VMS into our enterprise monitoring platform and would like guidance on the recommended architecture for collecting inventory, health, and live events at scale.
Our platform monitors and normalizes events, status, and alerts into a central monitoring system.
We are currently implementing using REST v3.
Inventory discovery is working successfully using:
- GET /rest/v3/system/info
- GET /rest/v3/devices
- GET /rest/v3/servers
We also tested:
- GET /rest/v3/servers/*/events
Questions:
- Recommended mechanism for live events at scale
We initially attempted to use:
- /ec2/transactionBus/websocket
However, we are receiving HTTP 403 during connection.
Questions:
- Is Transaction Bus still recommended for external integrations?
- Is it supported for Nx 6.x production integrations?
- What authentication method is required ?
- Are there permissions or configuration prerequisites?
- Is there a replacement mechanism that should be used instead?
- Event Log polling architecture
We tested:
GET /rest/v3/servers/*/events
This endpoint returns event history successfully.
Questions:
- Is polling this endpoint every 30 seconds an acceptable and supported architecture?
- Is there a recommended polling interval?
- Is event log internally indexed for large systems (10k+ cameras)
- Is eventTimestampUsec the recommended checkpoint mechanism?
- Detecting ONLINE recovery state
We do not clearly see how to determine:
- Camera recovered / online
- Server recovered / online
- Recording resumed
Questions:
- Which event types indicate recovery/online state?
- Is there an event pair model (offline + online)?
- Should recovery always be validated using status APIs?
- Lightweight status polling
We want to avoid polling full:
- /rest/v3/devices
- /rest/v3/servers
every 30 seconds for large sites.
Questions:
- Is there a lightweight endpoint recommended only for current status?
- Is there a projection/filter mechanism to request only:
- id
- status
- online/offline
- recording state
- Is there a dedicated health/status endpoint for monitoring platforms?
- Recommended architecture from Nx team
For large external monitoring systems, what architecture do you recommend:
Option A
Inventory sync
+
Transaction Bus
Option B
Inventory sync
+
Event log polling
Option C
Inventory sync
+
Status polling
-
Hi
This looks like a good use case for JSON RPC.
You'll find the relevant methods documented alongside each API endpoint in our API docs. We recommend using the latest version of Nx Witness / Nx Meta (6.1.2) to ensure full JSON RPC support.
Most of your questions should be covered directly in the API documentation — the descriptions, schemas, and request/response bodies are fairly detailed.
It might be help to take some time to explore those first will likely get you to answers in the document. If you run into anything specific after reviewing the docs, please send your questions/search the post here.
Thanks
0
Please sign in to leave a comment.
Comments
1 comment