I am writing to report a critical issue regarding the Search functionality in XProtect Professional+ 2025 R3. Our system, AIBridge (a multi-channel AI device registered via ONVIF), is experiencing a discrepancy where events are correctly triggered but do not appear in the Search results.
1. Environment Details
-
VMS: XProtect Professional+ 2025 R3 (Test Build)
-
Integration:
-
Events: Analytics Event Protocol (XML via TCP/HTTP on Port 9090)
-
Metadata: RTSP Metadata Track (ONVIF MetadataStream with Bounding Boxes)
-
2. Problem Description
-
Alarm Manager: Analytics Events
are received perfectly and visible in the real-time alarm list.
-
Smart Client Search: Searching for the same camera and time range yields “No search results”
-
Regression: This integration method worked correctly in previous versions. The issue has surfaced specifically in the 2025 R3 environment.
3. Technical Data Summary
We have confirmed that:
-
Analytics Event XML: Sent with a
<Value>tag containing detailed event strings. -
Metadata Stream: Properly includes
ObjectId,BoundingBox, andClass (Human/Vehicle)following ONVIF standards. -
Source Mapping: The
<Source>in the XML is correctly mapped to the camera registered in the Management Client.
4. Questions & Requests
-
Indexing Requirements: Has 2025 R3 introduced stricter requirements for indexing Analytics Events? Specifically, is a structured
<ID>within the<ObjectList>now mandatory to link the event with the Metadata for Search indexing? -
Schema Changes: Are there any updated schema requirements for the
AnalyticsEventprotocol to be compatible with the Centralized Search engine? -
Debugging Logs: Which specific server-side logs should we analyze to diagnose why events visible in the Alarm Manager are being omitted from the Search Index?
5. Additional Debugging Materials
We have prepared detailed debugging materials, including Packet Captures (Wireshark/PCAP) and internal logs, to assist in your investigation.
