[Jetson Orin / DeepStream 7.1] EMDX Analytics UI Missing Object Class / Operation / Rule Configuration — Is this a limitation of EMDX v1.2.9?

cyndi.yang · November 26, 2025, 1:40am

Hi NVIDIA team,

I am currently working with the official reference-workflow-and-resources_2.0.1.zip package and trying to integrate the following components on my Jetson device:

VST (nvcr.io/nvidia/jps/vst)
DeepStream 7.1
Redis (STREAM test)
EMDX Analytics (jps_v1.2.9)
emdx-webapi
LiveStream Web UI

The basic workflow is functioning, but the Analytics UI seems extremely limited, and I cannot access any rule-related configuration pages (Object class, Operation, Rule creation, etc.). I would like to clarify whether this behavior is expected for version 1.2.9 or if I am missing required components.

My Environment

JetPack Version: 6.1
DeepStream Version: 7.1
TensorRT Version: 10.3.0.30-1+cuda12.5
reference-workflow-and-resources: 2.0.1
Analytics container: nvcr.io/nvidia/jps/emdx-analytics:jps_v1.2.9

What Works Correctly

1. DeepStream-test5-app is running inference normally.
2. Redis STREAM test contains valid PeopleNet metadata
  - bbox / class / confidence present and correct
3. Analytics container is consuming the Redis stream
  - logs show datasink_0 with normal messages/sec
4. VST LiveStream UI works and ROI drawing works (but has no effect).

The Actual Problem: Analytics UI is Missing Most Features

The EMDX Analytics Web UI only shows a very minimal interface.

It does NOT include:

Object class selection (Person / Vehicle / Bike…)
Operation types (enter zone, exit zone, dwell time, counting…)
Rule creation / editing interface
Behavior configuration
Event logging / alerting
Analytics overlay in LiveStream

Because of this:

I can draw ROI, but it has no effect
I cannot create rules
No events are generated
LiveStream does not show analytics overlay

This appears very different from what is shown in NVIDIA solution demos and MOJ Analytics screenshots.

My Questions for NVIDIA

A. Is reference-workflow-and-resources_2.0.1 + EMDX Analytics v1.2.9 intentionally limited?

Is this version meant only as a demo without the full MOJ rule engine UI?

Is the rule configuration UI intentionally removed or disabled?

B. How can I enable the full rule UI (Object Class / Operation / Rule Engine)?

I could not find:

Any newer emdx-analytics image
Any 2.x / 3.x version
Any documentation describing how to enable MOJ UI in Jetson local deployment

Does the full MOJ Analytics require a different package or an Enterprise / Solutions deployment?

If so, how can it be obtained?

C. Should I use another workflow or version?

For example:

Is there a newer reference package (2.1 or newer)?
Is there a separate workflow for DeepStream + MOJ integration?
Is the Jetson-local workflow intentionally simplified?

Any official guidance would be greatly appreciated.

D. About VST overlay and analytics_server_address

VST has a config field:

"analytic_server_address": "http://<jetson-ip>:30080/emdx"

Even with a correct URL, LiveStream shows no analytics overlay.

Does VST overlay require a full MOJ rule engine to be enabled?

Or should it already work with jps_v1.2.9?

Summary — What I Need Help With

I want to confirm whether:

reference-workflow-and-resources_2.0.1 + EMDX Analytics v1.2.9
is a simplified demo without the full MOJ rule engine?

If I need the following features:

Object class selection
Operation types
Rule creation
Behavior analytics
Event triggering
Analytics overlay in LiveStream

Which version or deployment method should I use?

docker container

#camera_matadata

#Analytics engine is receiving Redis messages

deepstream Log Snippets

Thank you!

kesong · November 27, 2025, 5:09am

You can set tripwire and ROI counting in VST UI. Please refer this topic: Tripwire/ROI Not counting on Jetson Orin Nano - #3 by kesong

cyndi.yang · November 27, 2025, 5:52am

I followed the documentation you provided, but the current ROI value still stays at 0.

Redis also seems to have data, but I still can’t figure out where the problem is.

Please Help me.

kesong · November 27, 2025, 9:21am

Please set below with IP address instead of localhost.

“analytic_server_address”: “http://:30080/emdx”

cyndi.yang · November 28, 2025, 1:07am

I changed the URL, but it shows “Not Found”.
I also confirmed that the analytic_server_address setting is correct.
Here is the related information.
Could you please take a look and help me identify the issue?
Thank you.

analytic_server_address set detail

sudo docker logs emdx-webapi | tail -n 50

qsi@ubuntu:~$ sudo docker logs emdx-webapi | tail -n 50
[2025-11-27 05:36:09 +0000] [1] [INFO] Starting gunicorn 22.0.0
[2025-11-27 05:36:09 +0000] [1] [INFO] Listening at: http://0.0.0.0:5000 (1)
[2025-11-27 05:36:09 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2025-11-27 05:36:09 +0000] [7] [INFO] Booting worker with pid: 7
/usr/lib/python3.12/site-packages/tzlocal/unix.py:158: UserWarning: Can not find any timezone configuration, defaulting to UTC.
  warnings.warn('Can not find any timezone configuration, defaulting to UTC.')
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-26 03:00:00 UTC)" was missed by 1 day, 2:36:12.676322
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 1 day, 1:36:12.679923
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 1 day, 0:36:12.681770
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 23:36:12.681970
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 22:36:12.682083
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 21:36:12.682183
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 20:36:12.682281
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 19:36:12.682398
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 18:36:12.682527
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 17:36:12.682624
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 16:36:12.682711
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 15:36:12.682795
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 14:36:12.682878
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 13:36:12.682956
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 12:36:12.683033
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 11:36:12.683113
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 10:36:12.683190
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 9:36:12.683268
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 8:36:12.683362
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 7:36:12.683447
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 6:36:12.683525
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 5:36:12.683602
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 4:36:12.683677
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 3:36:12.683751
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 2:36:12.683822
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 1:36:12.683895
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 06:00:00 UTC)" was missed by 0:36:12.683965
[2025-11-27 05:36:15 +0000] [7] [INFO] Started server process [7]
[2025-11-27 05:36:15 +0000] [7] [INFO] Waiting for application startup.
[2025-11-27 05:36:15 +0000] [7] [INFO] Application startup complete.
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 12:00:00 UTC)" was missed by 0:00:02.613874
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 13:00:00 UTC)" was missed by 0:00:03.816355
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 14:00:00 UTC)" was missed by 0:00:02.924379
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-27 15:00:00 UTC)" was missed by 0:00:04.631231
Run time of job "ageing_job (trigger: cron[hour='*/1'], next run at: 2025-11-28 01:00:00 UTC)" was missed by 0:00:01.078030
2025-11-27 21:37:25,133 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.3,messages=91,duration=291877.0,reading=287263.6,processing(sum=4613.4, mean=50.7,max=4553.5,min=0.5),lag(mean=52.9,max=4557.2,min=1.7)
2025-11-27 21:37:25,133 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=291877.0,reading=291824.2,processing(sum=52.8, mean=5.9,max=11.7,min=1.2),lag(mean=7.3,max=13.6,min=2.8)
2025-11-27 21:44:09,987 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=95,duration=404854.1,reading=404790.6,processing(sum=63.5, mean=0.7,max=1.5,min=0.4),lag(mean=3.0,max=7.4,min=1.9)
2025-11-27 21:44:09,988 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=5,duration=404854.1,reading=404828.9,processing(sum=25.2, mean=5.0,max=6.3,min=1.3),lag(mean=6.3,max=8.0,min=1.9)
2025-11-27 21:56:36,508 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.1,messages=91,duration=746519.5,reading=744575.6,processing(sum=1943.9, mean=21.4,max=1883.1,min=0.4),lag(mean=42.2,max=1885.3,min=1.8)
2025-11-27 21:56:36,508 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=746519.5,reading=746017.6,processing(sum=501.9, mean=55.8,max=450.6,min=5.7),lag(mean=57.3,max=452.0,min=7.1)
2025-11-27 22:07:14,145 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.1,messages=93,duration=637636.4,reading=634626.3,processing(sum=3010.1, mean=32.7,max=2885.7,min=0.5),lag(mean=74.4,max=2887.3,min=1.5)
2025-11-27 22:07:14,145 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=637636.4,reading=636612.8,processing(sum=1023.6, mean=127.9,max=908.2,min=1.4),lag(mean=243.0,max=924.9,min=2.5)
2025-11-27 22:18:27,716 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.1,messages=97,duration=673571.0,reading=671429.5,processing(sum=2141.4, mean=23.3,max=2008.6,min=0.4),lag(mean=134.3,max=2011.2,min=1.9)
2025-11-27 22:18:27,717 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=673571.0,reading=673541.4,processing(sum=29.5, mean=3.7,max=6.2,min=1.2),lag(mean=6.0,max=8.8,min=2.6)
2025-11-27 22:26:15,718 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=96,duration=468001.2,reading=465468.3,processing(sum=2532.9, mean=27.2,max=2470.7,min=0.5),lag(mean=126.2,max=2473.0,min=1.9)
2025-11-27 22:26:15,719 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=7,duration=468001.2,reading=467960.3,processing(sum=40.9, mean=5.8,max=13.7,min=1.5),lag(mean=7.1,max=14.9,min=3.0)
2025-11-27 22:33:22,239 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=98,duration=426520.3,reading=412303.2,processing(sum=14217.1, mean=156.2,max=8467.8,min=0.5),lag(mean=439.0,max=8469.9,min=1.8)
2025-11-27 22:33:22,240 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=10,duration=426520.3,reading=424019.9,processing(sum=2500.4, mean=250.0,max=2171.6,min=1.5),lag(mean=1097.8,max=8685.5,min=2.7)
2025-11-27 22:53:18,440 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.1,messages=95,duration=1196199.9,reading=1196103.1,processing(sum=96.8, mean=1.0,max=34.2,min=0.4),lag(mean=3.4,max=35.6,min=1.7)
2025-11-27 22:53:18,441 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=5,duration=1196199.9,reading=1196178.7,processing(sum=21.2, mean=4.2,max=6.4,min=1.4),lag(mean=5.5,max=7.8,min=2.4)
2025-11-27 22:59:49,105 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=92,duration=390664.3,reading=386191.2,processing(sum=4473.0, mean=48.6,max=3200.9,min=0.5),lag(mean=84.2,max=3204.1,min=1.6)
2025-11-27 22:59:49,106 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=390664.3,reading=390503.3,processing(sum=161.0, mean=20.1,max=131.7,min=1.5),lag(mean=21.4,max=132.4,min=2.7)
2025-11-27 23:10:18,972 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.1,messages=92,duration=629865.8,reading=628532.2,processing(sum=1333.7, mean=14.5,max=1274.2,min=0.5),lag(mean=16.8,max=1279.9,min=1.8)
2025-11-27 23:10:18,972 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=629865.8,reading=629300.8,processing(sum=565.0, mean=70.6,max=301.2,min=1.2),lag(mean=230.1,max=1491.7,min=2.7)
2025-11-27 23:16:39,855 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.3,messages=96,duration=380882.4,reading=380297.0,processing(sum=585.4, mean=6.6,max=364.4,min=0.5),lag(mean=64.9,max=1117.4,min=1.6)
2025-11-27 23:16:39,855 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=11,duration=380882.4,reading=379483.3,processing(sum=1399.0, mean=127.2,max=1139.6,min=1.5),lag(mean=128.5,max=1141.1,min=2.8)
2025-11-27 23:21:02,947 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.4,messages=95,duration=263091.3,reading=259707.3,processing(sum=3384.0, mean=37.2,max=1695.5,min=0.5),lag(mean=52.0,max=1697.6,min=1.6)
2025-11-27 23:21:02,947 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=263091.3,reading=262613.5,processing(sum=477.8, mean=53.1,max=383.9,min=1.3),lag(mean=406.5,max=1676.5,min=2.5)
2025-11-27 23:24:47,834 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.5,messages=106,duration=224886.6,reading=223106.8,processing(sum=1779.9, mean=18.9,max=1478.1,min=0.5),lag(mean=141.9,max=1480.1,min=1.7)
2025-11-27 23:24:47,835 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=6,duration=224886.6,reading=224118.7,processing(sum=767.9, mean=128.0,max=423.9,min=1.8),lag(mean=167.2,max=556.4,min=2.9)
2025-11-27 23:27:59,753 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.5,messages=91,duration=191918.2,reading=190384.2,processing(sum=1534.0, mean=16.9,max=1466.6,min=0.5),lag(mean=19.2,max=1468.2,min=1.7)
2025-11-27 23:27:59,754 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=191918.2,reading=191738.6,processing(sum=179.6, mean=20.0,max=128.6,min=1.5),lag(mean=21.3,max=129.5,min=2.5)
2025-11-27 23:31:53,900 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.4,messages=92,duration=234146.0,reading=234083.4,processing(sum=62.7, mean=0.7,max=1.5,min=0.5),lag(mean=3.0,max=7.7,min=1.5)
2025-11-27 23:31:53,900 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=234146.0,reading=233923.0,processing(sum=223.0, mean=27.9,max=198.8,min=1.3),lag(mean=29.2,max=200.1,min=2.1)
2025-11-27 23:34:38,580 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.6,messages=97,duration=164679.3,reading=159782.8,processing(sum=4896.5, mean=54.4,max=2792.3,min=0.5),lag(mean=111.5,max=2794.7,min=1.9)
2025-11-27 23:34:38,580 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.1,messages=11,duration=164679.3,reading=163441.1,processing(sum=1238.2, mean=112.6,max=780.6,min=1.4),lag(mean=366.4,max=2791.0,min=2.7)
2025-11-27 23:44:02,161 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=92,duration=563580.9,reading=563519.5,processing(sum=61.4, mean=0.7,max=1.0,min=0.5),lag(mean=3.1,max=7.9,min=1.7)
2025-11-27 23:44:02,162 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=8,duration=563580.9,reading=563549.0,processing(sum=31.8, mean=4.0,max=7.3,min=1.5),lag(mean=5.6,max=9.5,min=2.6)
2025-11-27 23:48:44,152 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.3,messages=95,duration=281990.6,reading=281482.9,processing(sum=507.6, mean=5.6,max=449.1,min=0.5),lag(mean=74.5,max=1409.4,min=1.6)
2025-11-27 23:48:44,153 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=281990.6,reading=279164.4,processing(sum=2826.1, mean=314.0,max=2758.9,min=1.1),lag(mean=364.5,max=3202.2,min=2.3)
2025-11-27 23:58:22,018 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=95,duration=577864.8,reading=577805.3,processing(sum=59.5, mean=0.7,max=1.4,min=0.5),lag(mean=14.9,max=330.4,min=1.9)
2025-11-27 23:58:22,018 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=577864.8,reading=577486.2,processing(sum=378.6, mean=42.1,max=347.0,min=1.3),lag(mean=43.7,max=351.1,min=2.8)
2025-11-28 00:07:59,182 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=89,duration=577163.3,reading=575792.6,processing(sum=1370.7, mean=15.4,max=1301.5,min=0.4),lag(mean=17.9,max=1303.3,min=1.6)
2025-11-28 00:07:59,188 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=11,duration=577163.3,reading=577073.1,processing(sum=90.2, mean=8.2,max=51.0,min=1.5),lag(mean=127.1,max=1294.4,min=2.9)
2025-11-28 00:12:15,508 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.4,messages=96,duration=256319.0,reading=256043.3,processing(sum=275.7, mean=3.0,max=215.7,min=0.4),lag(mean=93.7,max=1765.0,min=1.7)
2025-11-28 00:12:15,508 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=256319.0,reading=254397.4,processing(sum=1921.6, mean=213.5,max=1788.2,min=1.1),lag(mean=214.8,max=1789.3,min=2.6)
2025-11-28 00:15:28,179 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.6,messages=107,duration=192670.4,reading=189751.5,processing(sum=2918.9, mean=32.4,max=2074.7,min=0.5),lag(mean=80.1,max=2076.4,min=1.7)
2025-11-28 00:15:28,179 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.1,messages=11,duration=192670.4,reading=192234.5,processing(sum=435.9, mean=39.6,max=400.1,min=1.3),lag(mean=70.2,max=401.1,min=2.6)
2025-11-28 00:24:27,003 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=93,duration=538823.9,reading=530209.4,processing(sum=8614.4, mean=93.6,max=4417.9,min=0.4),lag(mean=173.8,max=4420.2,min=1.8)
2025-11-28 00:24:27,004 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=9,duration=538823.9,reading=535273.3,processing(sum=3550.6, mean=394.5,max=1091.0,min=5.7),lag(mean=469.0,max=1092.3,min=7.2)
2025-11-28 00:32:53,878 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=117,duration=506874.0,reading=484529.6,processing(sum=22344.4, mean=245.5,max=5076.9,min=0.4),lag(mean=951.1,max=6124.2,min=1.7)
2025-11-28 00:32:53,878 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=12,duration=506874.0,reading=488198.4,processing(sum=18675.7, mean=1556.3,max=6734.1,min=1.0),lag(mean=2374.8,max=6735.1,min=2.0)
2025-11-28 00:47:18,109 INFO [7 datasink_2] (messageRouter.py:86) - stream=test,mesages/sec=0.2,messages=131,duration=864230.7,reading=817642.6,processing(sum=46588.0, mean=517.6,max=14418.6,min=0.4),lag(mean=3261.0,max=16964.7,min=1.9)
2025-11-28 00:47:18,649 INFO [7 datasink_2] (messageRouter.py:86) - stream=emdx_trajectory,mesages/sec=0.0,messages=13,duration=864230.7,reading=807578.4,processing(sum=56652.3, mean=4357.9,max=17574.5,min=1.7),lag(mean=7301.3,max=22444.0,min=3.2)

sudo docker ps

kesong · December 2, 2025, 7:59am

Please share the log of VST container to check if VST can get the count from emdx.

Topic		Replies	Views
VST EMDX-Analytics failure Metropolis Microservices for Jetson deepstream	4	162	May 13, 2025
JPS 2.0 - emdx analytics issue Metropolis Microservices for Jetson nvbugs , jetson , deepstream	3	200	June 24, 2025
VST UI Fails to Load ROI and Tripwire Configurations - "Failed to get tripwire. Try again Metropolis Microservices for Jetson deepstream	14	273	July 31, 2025
Cannot access FOV API Endpoints Metropolis Microservices for Jetson deepstream	7	149	September 23, 2024
Emdx analytics webapi not working correctly Metropolis Microservices for Jetson jetpack , jetson , ainvr , jetson-orin	10	248	January 22, 2025
Deepstream occupancy analytics running issues DeepStream SDK	2	664	April 25, 2022
Jetson Neno AI NVR - How to add deepstream processing for RTSP streams discovered in VST Metropolis Microservices for Jetson deepstream	19	225	November 18, 2025
Analytics not working on VST Web UI Metropolis Microservices for Jetson	3	396	May 15, 2024
AINVR emdx webapi and emdx analytics not working correctly Metropolis Microservices for Jetson jetson , deepstream	2	97	January 22, 2025
Ainvr analytics service, retrieve ROI information from redis Metropolis Microservices for Jetson data-analytics , deepstream	6	173	October 29, 2024