Analytic Object Detected - HTTP Request missing information
Completed
Good afternoon, very simply put, on HTTP Requests, I have tried multiple placeholders however nothing seems to populate the correct system/device information when transmitting the HTTP Request. I've tried the below, but nothing is actually populating the necessary information. I only see a duplicate of the event placeholder titles in my HTTP server logs. Can we confirm this is currently not supported, or not available?
{event.cameraId}
{event.cameraName}
{event.eventType}
{event.eventName}
{event.source}
{event.caption}
{event.description}
-
Thank you for your post.
We'll need a bit more information regarding what your specific concern is. I understand that it appears to be with HTTP requests being received (or sent) within the analytics object detected, but there's no information regarding what you're currently using within a rule configuration, etc.
Please provide us with further details and if we're able to provide a quick response then we'll do so here.
Thank you!
0 -
Thanks Michael. Appreciate the requested information. This is for HTTP Request as an action (sending).
I have events configured for an Analytics Object Detected (Person), where the action is to perform an HTTP Request. When I populate the body of the HTTP request with the event placeholders, they do not pull the required information. Instead, I get a duplicate of the HTTP body in my server log files (also attached). I tried formatting the placeholders in two different ways, both screenshots attached.This becomes a problem when scaling this event for 100's of cameras. I'd ideally like to configure the event rule once, and just select the cameras that can detect a person to trigger the http action. This makes applying the rule to 100's of cameras just a few mouse clicks, whereas typing information for each camera can be exhaustive especially during testing where the rule can change. Screenshot attached for reference.
0 -
Thank you for the additional details.
In the second screenshot I can see that you included the JSON string that would be used for a createEvent API call to the Nx API (with the idea being that you use one rule to trigger another action such as writing to log for example).
Can you confirm if your intention is to utilize our own API within the Do HTTP Request? Or are your plans to implement a 3rd party that will instead receive a message whenever the Analytics Object Detection rule triggers?
Thank you.
0 -
Thank you Michael!
The plans are to have the HTTP request action (outbound) send a message, which will be received by a 3rd party HTTP service when the Object Detection rule is triggered.
Person Detected-->Event Rule-->HTTP Request-->3rd Party HTTP Service
Admittedly, I was searching for ways to automatically populate the HTTP Request action. The ideal information would be Camera Name/Camera ID, Object Detected Start and Object Detected Stop (similar to how Motion Detection can send a start and stop message). This is helpful to automate when turning this rule on for large systems (100+ cameras).
0 -
Thank you for the confirmation.
We actually have another community post here that is detailing this exact scenario and you may benefit from reviewing the same information and implementing the same syntax/workflow process. In short, you will want to use a JSON syntax for the HTTP Content section and if you utilize it in the manner shown in this POST, then we would expect it to work.
If you run into issues like what's described by the other user's reply in that post, then the next step from our end will likely be to convert this post to a support ticket and we can handle things from there via the support process.
Thank you.
0
Post is closed for comments.
Comments
5 comments