Skip to content

Commit 71e406b

Browse files
mtlljmmtlljm
committed
Improve the process for importing Grafana dashboard examples
Update grafana.json to add placeholders to configure internal and external server urls update README.md for each to point to DASHBOARD.md add new readme on how to configure and import the dashboards Signed-off-by: mtlljm <liam.mcgregor@sas.com>
1 parent d06a2f3 commit 71e406b

11 files changed

Lines changed: 119 additions & 70 deletions

File tree

‎EndToEndExamples/DASHBOARD.md‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# Importing the Grafana Dashboard
2+
3+
Before you import the dashboard, you need to update the `grafana.json` file for your environment.
4+
5+
## 1. Download the Dashboard File
6+
7+
- Download the `grafana.json` file to your system.
8+
9+
## 2. Update Placeholders in the Dashboard File
10+
11+
Depending on your datasource, follow the appropriate steps below.
12+
13+
### A. If Using an Internal Discovery Service
14+
15+
Replace all instances of `%NAMESPACE%` with the Kubernetes namespace where SAS Event Stream Processing and Grafana are running.
16+
17+
**How to Replace:**
18+
19+
- **Manually:** Open `grafana.json` in a text editor, find and replace all occurrences of `%NAMESPACE%` with your namespace.
20+
- **Command Line:**
21+
- **Windows (PowerShell):**
22+
```
23+
(Get-Content grafana.json) -replace '%NAMESPACE%', 'your-namespace' | Set-Content grafana.json
24+
```
25+
- **Linux (bash):**
26+
```
27+
sed -i 's/%NAMESPACE%/your-namespace/g' grafana.json
28+
```
29+
30+
### B. If Using an External Discovery Service URL
31+
32+
Replace all instances of `%DOMAIN%` with the domain name where your ESP Project is running.
33+
34+
**How to Replace:**
35+
36+
- **Manually:** Open `grafana.json` in a text editor, find and replace all occurrences of `%DOMAIN%` with your domain.
37+
- **Command Line:**
38+
- **Windows (PowerShell):**
39+
```
40+
(Get-Content grafana.json) -replace '%DOMAIN%', 'my.server.com' | Set-Content grafana.json
41+
```
42+
- **Linux (bash):**
43+
```
44+
sed -i 's/%DOMAIN%/my.server.com/g' grafana.json
45+
```
46+
47+
## 3. Import the Dashboard into Grafana
48+
49+
1. In Grafana, go to **Dashboards** from the navigation bar.
50+
2. Click **New**.
51+
3. Select **Import** from the dropdown list.
52+
4. Click **Upload dashboard JSON file** and select your updated `grafana.json`.
53+
5. Click **Import**.
54+
55+
---
56+
**Summary:**
57+
Download the dashboard file, update the placeholders for your environment, and import it into Grafana.

‎EndToEndExamples/connectivity_analytics/README.md‎

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -290,12 +290,8 @@ When you test the project, the results appear on separate tabs. The following fi
290290
![w_rules tab](img/w_rules.png "w_rules tab")
291291

292292
## Next Steps
293-
Alerts, model performance, and streaming data can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Do the following steps to import [grafana.json](grafana.json) to Grafana:
294-
1. From the navigation bar, click **Dashboards**.
295-
2. Click **New**.
296-
3. From the drop down list, select **Import**.
297-
4. Click **Upload dashboard JSON file** and select `grajana.json` using the file selector.
298-
5. Click **Import**.
293+
Alerts, model performance, and streaming data can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin).
294+
Follow the instructions in [DASHBOARD.md](../DASHBOARD.md) to import the dashboard into Grafana.
299295

300296
The following figures show an example of a Grafana dashboard:
301297
![streaming data and distribution](img/grafana-1.png "streaming data and distribution")

‎EndToEndExamples/connectivity_analytics/grafana.json‎

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -112,9 +112,9 @@
112112
"type": "sasesp-plugin",
113113
"uid": "P8052081D5634A876"
114114
},
115-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
115+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
116116
"fields": [],
117-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
117+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
118118
"projectName": "connectivity_analytics",
119119
"refId": "A",
120120
"windowName": "w_cmp_stream"
@@ -195,9 +195,9 @@
195195
"type": "sasesp-plugin",
196196
"uid": "P8052081D5634A876"
197197
},
198-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
198+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
199199
"fields": [],
200-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
200+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
201201
"projectName": "connectivity_analytics",
202202
"refId": "A",
203203
"windowName": "w_rate"
@@ -320,9 +320,9 @@
320320
"type": "sasesp-plugin",
321321
"uid": "P8052081D5634A876"
322322
},
323-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
323+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
324324
"fields": [],
325-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
325+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
326326
"projectName": "connectivity_analytics",
327327
"refId": "A",
328328
"windowName": "w_aggr_stats"
@@ -393,9 +393,9 @@
393393
"type": "sasesp-plugin",
394394
"uid": "P8052081D5634A876"
395395
},
396-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
396+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
397397
"fields": [],
398-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
398+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
399399
"projectName": "connectivity_analytics",
400400
"refId": "A",
401401
"windowName": "w_change_latency"
@@ -535,9 +535,9 @@
535535
"type": "sasesp-plugin",
536536
"uid": "P8052081D5634A876"
537537
},
538-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
538+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
539539
"fields": [],
540-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
540+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
541541
"projectName": "connectivity_analytics",
542542
"refId": "A",
543543
"windowName": "w_rules"
@@ -718,9 +718,9 @@
718718
"type": "sasesp-plugin",
719719
"uid": "P8052081D5634A876"
720720
},
721-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
721+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
722722
"fields": [],
723-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
723+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
724724
"projectName": "connectivity_analytics",
725725
"refId": "A",
726726
"windowName": "w_rules"
@@ -877,9 +877,9 @@
877877
"type": "sasesp-plugin",
878878
"uid": "P8052081D5634A876"
879879
},
880-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
880+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
881881
"fields": [],
882-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
882+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
883883
"projectName": "connectivity_analytics",
884884
"refId": "A",
885885
"windowName": "w_rules"
@@ -968,9 +968,9 @@
968968
"type": "sasesp-plugin",
969969
"uid": "P8052081D5634A876"
970970
},
971-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
971+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
972972
"fields": [],
973-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
973+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
974974
"projectName": "connectivity_analytics",
975975
"refId": "A",
976976
"windowName": "w_rules"
@@ -1113,9 +1113,9 @@
11131113
"type": "sasesp-plugin",
11141114
"uid": "P8052081D5634A876"
11151115
},
1116-
"externalServerUrl": "wss://iot.viya-azure-gpu.unx.sas.com/SASEventStreamProcessingServer/esps-connectivity-5fanalytics",
1116+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-connectivity-5fanalytics/eventStreamProcessing/v2",
11171117
"fields": [],
1118-
"internalServerUrl": "wss://esps-connectivity-5fanalytics.sas-viya:443",
1118+
"internalServerUrl": "wss://esps-connectivity-5fanalytics.%NAMESPACE%:443/eventStreamProcessing/v2",
11191119
"projectName": "connectivity_analytics",
11201120
"refId": "A",
11211121
"windowName": "w_rules"
@@ -1188,4 +1188,4 @@
11881188
"uid": "e6522183-cf82-49ba-bb87-205d9726f6d9",
11891189
"version": 6,
11901190
"weekStart": ""
1191-
}
1191+
}

‎EndToEndExamples/mcp/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,14 +77,14 @@ The following figures show SAS Retrieval Agent Manager accessing the MCP tools e
7777
![SAS RAM MCP query details](img/RAM_MCP_Query_Details.png "SAS RAM MCP query details")
7878

7979
## Visualizing Objects in Grafana
80-
The sailing boats and areas of interest can be visualized using [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Import the `grafana.json` dashboard file to Grafana. The `grafana.json` file references the `sailing-areas-of-interest.geojson` file, which defines the areas of interest.
80+
The sailing boats and areas of interest can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). The [dashboard.json](grafana.json) file references the [sailing-areas-of-interest.geojson](sailing-areas-of-interest.geojson) file, which defines the areas of interest.
8181

82-
**NOTE:** This dashboard was created using standalone SAS Event Stream Processing running in the same namespace as Grafana. If you are using a different environment, such as the SAS Viya platform, you must re-create the queries because the connection URLs differ.
82+
Follow the instructions in [DASHBOARD.md](../DASHBOARD.md) to import the dashboard into Grafana.
8383

8484
<img alt="Sailing dashboard" src="img/sailing-dashboard.png" width="75%" height="75%">
8585

8686
## Additional Resources
8787

8888
- The [Using a Geofence to Find Wanted Vehicles](https://github.com/sassoftware/esp-studio-examples/tree/main/Advanced/geofence) example provides a more detailed discussion of the settings for a Geofence window and for connector orchestration.
8989
- For more information about the Geofence window, see [SAS Help Center: Using Geofence Windows](https://documentation.sas.com/?cdcId=espcdc&cdcVersion=default&docsetId=espcreatewindows&docsetTarget=p0xru6q01dkxknn1t8gqo2q4zfu6).
90-
- For more information about MCP support in SAS Retrieval Agent Manager, see [SAS Help Center: Working with MCP Tools](https://go.documentation.sas.com/doc/en/ragntmgrcdc/default/ragntmgrug/n1l22bifonn2hjn1lquqow5vmxp2.htm?fromDefault=).
90+
- For more information about MCP support in SAS Retrieval Agent Manager, see [SAS Help Center: Working with MCP Tools](https://go.documentation.sas.com/doc/en/ragntmgrcdc/default/ragntmgrug/n1l22bifonn2hjn1lquqow5vmxp2.htm?fromDefault=).

‎EndToEndExamples/mcp/grafana.json‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -177,10 +177,10 @@
177177
"uid": "${DS_SAS_EVENT STREAM PROCESSING DATASOURCE}"
178178
},
179179
"fields": [],
180-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
180+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
181181
"projectName": "sailing_with_mcp",
182182
"refId": "A",
183-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
183+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
184184
"windowName": "Boat1"
185185
}
186186
],
@@ -467,10 +467,10 @@
467467
"uid": "${DS_SAS_EVENT STREAM PROCESSING DATASOURCE}"
468468
},
469469
"fields": [],
470-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
470+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
471471
"projectName": "sailing_with_mcp",
472472
"refId": "A",
473-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
473+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
474474
"windowName": "Geofence_Area_Check"
475475
}
476476
],
@@ -596,10 +596,10 @@
596596
},
597597
"fieldName": "speed",
598598
"fields": [],
599-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
599+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
600600
"projectName": "sailing_with_mcp",
601601
"refId": "A",
602-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
602+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
603603
"windowName": "Boat2"
604604
}
605605
],
@@ -805,10 +805,10 @@
805805
},
806806
"fieldName": "speed",
807807
"fields": [],
808-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
808+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
809809
"projectName": "sailing_with_mcp",
810810
"refId": "A",
811-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
811+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
812812
"windowName": "Boat3"
813813
}
814814
],
@@ -1011,10 +1011,10 @@
10111011
},
10121012
"fieldName": "speed",
10131013
"fields": [],
1014-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1014+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
10151015
"projectName": "sailing_with_mcp",
10161016
"refId": "A",
1017-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1017+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
10181018
"windowName": "Boat4"
10191019
}
10201020
],
@@ -1212,10 +1212,10 @@
12121212
},
12131213
"fieldName": "BoatNumber",
12141214
"fields": [],
1215-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1215+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
12161216
"projectName": "sailing_with_mcp",
12171217
"refId": "A",
1218-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1218+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
12191219
"windowName": "Last_Speeding_Event"
12201220
}
12211221
],
@@ -1395,10 +1395,10 @@
13951395
},
13961396
"fieldName": "BoatNumber",
13971397
"fields": [],
1398-
"internalServerUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1398+
"internalServerUrl": "wss://esps-sailing-5fwith-5fmcp.%NAMESPACE%:443/eventStreamProcessing/v2",
13991399
"projectName": "sailing_with_mcp",
14001400
"refId": "A",
1401-
"serverUrl": "ws://esps-sailing-5fwith-5fmcp:80",
1401+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-sailing-5fwith-5fmcp/eventStreamProcessing/v2",
14021402
"windowName": "Last_Exclusion_Violation"
14031403
}
14041404
],

‎EndToEndExamples/onnx_object_detection/README.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -164,13 +164,12 @@ If it takes a long time for events to appear in test mode, contact your system a
164164
Geofences are virtual perimeters and can be used, for example, to trigger alerts when persons are detected in prohibited areas or when cars are parked in the wrong spot. For more information, see [Using Geofence Windows](https://go.documentation.sas.com/doc/en/espcdc/v_037/espcreatewindows/p0xru6q01dkxknn1t8gqo2q4zfu6.htm).
165165

166166
### Visualizing Objects in Grafana (recommended)
167-
The detected objects can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Import the [grafana.json](grafana.json) dashboard file to Grafana.
167+
The detected objects can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Follow the instructions in [DASHBOARD.md](../DASHBOARD.md) to import the dashboard into Grafana.
168168

169169
---
170170
**NOTE:**
171171
- This dashboard uses the [Base64 Image/Video/Audio/PDF](https://grafana.com/grafana/plugins/volkovlabs-image-panel/) plug-in for Grafana.
172172
- This dashboard was created using standalone SAS Event Stream Processing, running in the same namespace as Grafana. If you are using a different environment, such as the SAS Viya platform, you must recreate the queries because the connection URLs will differ.
173-
174173
---
175174

176175
The dashboard includes the following panel:

‎EndToEndExamples/onnx_object_detection/grafana.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,10 +102,10 @@
102102
},
103103
"fields": [],
104104
"hide": false,
105-
"internalServerUrl": "ws://esps-computer-5fvision-5fwith-5fonnx:80",
105+
"internalServerUrl": "wss://esps-computer-5fvision-5fwith-5fonnx.%NAMESPACE%:443/eventStreamProcessing/v2",
106106
"projectName": "computer_vision_with_onnx",
107107
"refId": "A",
108-
"serverUrl": "ws://esps-computer-5fvision-5fwith-5fonnx:80",
108+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-computer-5fvision-5fwith-5fonnx/eventStreamProcessing/v2",
109109
"windowName": "w_annotate"
110110
}
111111
],

‎EndToEndExamples/onnx_pose_estimation/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ If it takes a long time for events to appear in test mode, contact your system a
105105
From the detected keypoints, you could predict the activity of a person. For example, you could check whether someone is picking up an object ergonomically or detect whether someone performs a certain yoga pose. These findings can be combined with a [Geofence window](https://go.documentation.sas.com/doc/en/espcdc/default/espcreatewindows/p0xru6q01dkxknn1t8gqo2q4zfu6.htm) to determine whether the activity takes place in a certain region of the frame.
106106

107107
### Visualizing Objects in Grafana (recommended)
108-
The detected objects can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Import the [grafana.json](grafana.json) dashboard file to Grafana.
108+
The detected objects can be visualized using the [SAS Event Stream Processing Data Source Plug-in for Grafana](https://github.com/sassoftware/grafana-esp-plugin). Follow the instructions in [DASHBOARD.md](../DASHBOARD.md) to import the dashboard into Grafana.
109109

110110
---
111111
**NOTE:**

‎EndToEndExamples/onnx_pose_estimation/grafana.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,10 +101,10 @@
101101
"uid": "${DS_SAS_EVENT STREAM PROCESSING DATASOURCE}"
102102
},
103103
"fields": [],
104-
"internalServerUrl": "ws://esps-pose-5festimation-5fwith-5fonnx:80",
104+
"internalServerUrl": "wss://esps-pose-5festimation-5fwith-5fonnx.%NAMESPACE%:443/eventStreamProcessing/v2",
105105
"projectName": "pose_estimation_with_onnx",
106106
"refId": "A",
107-
"serverUrl": "ws://esps-pose-5festimation-5fwith-5fonnx:80",
107+
"externalServerUrl": "wss://%DOMAIN%:443/SASEventStreamProcessingServer/esps-pose-5festimation-5fwith-5fonnx/eventStreamProcessing/v2",
108108
"windowName": "w_annotate"
109109
}
110110
],

0 commit comments

Comments
 (0)