You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/blog/releases/2025.X/2025.7.md
+63-81Lines changed: 63 additions & 81 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "2025.7"
3
3
linkTitle: "2025.7"
4
-
date: 2025-08-15
4
+
date: 2025-08-11
5
5
author: Paul Arnold ([@paulmarnold](https://twitter.com/paulmarnold))
6
6
---
7
7
@@ -24,7 +24,18 @@ Installation artefacts can be requested by raising a case in the [{{% ctx %}} Se
24
24
* Observability
25
25
* Documentation
26
26
27
-
<!-- TBC -->
27
+
This release introduces multiple new features to the {{% ctx %}} Platform:
28
+
29
+
* The [{{% ctx %}} Trigger Service now supports loading MIBs to translate SNMP traps][Capability - Support for MIBs loading to the {{% ctx %}} Trigger Service].
30
+
* The [trap details now includes a ReceivedAt field][Capability - Added ReceivedAt to trap details].
31
+
* The [SSH Block now supports non-printable characters in the command][Capability - Added support for non-printable characters in SSH block].
32
+
* The [Log Event Block now allows the user to provide a path to log to][Capability - Added support for user to provide a log path on Log Event blocks].
33
+
* The [Running Executions grid now allows the user to select multiple executions and stop them at once][Capability - Added support for stopping multiple executions].
34
+
35
+
The [Performance][] of the {{% ctx %}} has been improved by:
36
+
37
+
*[batching the stopping of multiple executions][Performance - Batched stopping executions].
38
+
*[improving the performance of the monitoring service][Performance - Improved performance of monitoring service].
28
39
29
40
### Components
30
41
@@ -68,16 +79,12 @@ Installation artefacts can be requested by raising a case in the [{{% ctx %}} Se
68
79
69
80
#### Capability
70
81
71
-
##### Support for MIBs loading to the {{% ctx %}} Trigger Service
72
-
73
-
Within the server hosting [{{% ctx %}} Gateway][Gateway], the user can now add `MIBs` to the preconfigured `MIBs` folder, which is created on first start up of [{{% ctx %}} Gateway][Gateway] and can be found in `%PROGRAMDATA%\Cortex\Configuration\Triggers\SNMP\MIBs`, including sub-folders.
74
-
75
-
The `MIBs` are loaded by [{{% ctx %}} Gateway][Gateway] on:
82
+
##### Support for SNMP MIB loading and OID translation
76
83
77
-
* Startup
78
-
* File change
79
-
80
-
When `MIBs` are loaded on [{{% ctx %}} Gateway][Gateway], they are sent to the [{{% ctx %}} Trigger Service][] then used to translate `SNMP` traps.
84
+
Within the server hosting [{{% ctx %}} Gateway][Gateway], the user can now add `MIBs` to the preconfigured `MIBs` folder, which is created on first start up of [{{% ctx %}} Gateway][Gateway] and can be found in `%PROGRAMDATA%\Cortex\Configuration\Triggers\SNMP\MIBs`.
85
+
The `MIBs` folder can contain multiple `MIB` files, and can be organised using sub-folders.
86
+
Files with a `.mib` extension will be loaded by [{{% ctx %}} Gateway][Gateway] on startup, then sent to the [{{% ctx %}} Trigger Service][] where they are used to translate `OIDs` in `SNMP` traps into a more human-readable format.
87
+
Changes to any of the `.mib` files, or new files added, or existing files deleted will be detected and reloaded automatically.
81
88
82
89
Affected Components:
83
90
@@ -89,56 +96,71 @@ Affected Components:
89
96
<!-- 37008 Trigger Service - Add Mib Node Store - Batch Transactions to Improve Performance -->
90
97
<!-- 35662 Trigger Service - Replicate Mib Nodes to all partitions -->
91
98
92
-
##### Added ReceivedAt to trap details
99
+
##### Added ReceivedAt property to SNMP Trap Details
93
100
94
-
A new field has been added to the trap details, which is called `ReceivedAt`. This field contains the date and time that the trap was received by the [{{% ctx %}} Trigger Service][] in the `ISO 8601 format`.
101
+
A new `ReceivedAt` property has been added to the SNMP Trap Details that are passed as an input variable of a flow configured to be run by SNMP traps matching a configured an SNMP trigger.
102
+
This property contains the date and time that the trap was received by the [{{% ctx %}} Trigger Service][] in the `ISO 8601 Standard`.
95
103
96
104
Affected Components:
97
105
98
106
<!-- Add field to trap details -->
99
107
<!-- 36323 Trigger Service - Add ReceivedAt to trap details -->
100
108
101
-
##### Added support for non-printable characters in SSH block
109
+
##### Added support for non-printable characters in Execute SSH Command Block
102
110
103
-
The [SSH Block][] has been updated to support non-printable characters in the command that is executed.
104
-
This is useful for commands that contain non-printable characters, such as passwords or other sensitive information.
111
+
The [Execute SSH Command Block][] has been updated to support commands that either don't echo back or contain non-printable characters in the response. An example of this is when a command is run that does not return any output, such as `echo -n ""`, or when a command contains non-printable characters, such as a password.
105
112
106
113
{{% alert title="Note" %}}
107
-
The `StrictResponseMatching` and `ResponseGracePeriod` options can now be added in the advanced block properties `Configuration Settings`, allowing it to be overwritten on a per block basis using the advanced `Configuration Settings` block property of the {{< ahref path="Cortex.Reference.Blocks.Ssh.ExecuteSshCommand.ExecuteSshCommandBlock.ConfigurationSettings" version="2025.7" title="SSH" >}}.
108
-
<!-- TODO - See whether this is too much, or needs docs -->
109
-
`StrictResponseMatching` can be set to `false`, allowing to match empty responses. Default is `true`.
110
-
`ResponseGracePeriod` can be set to any number, which is the number of milliseconds to wait for a response before checking the response. Default is `0`.
114
+
The `StrictResponseMatching` option can now be added in the advanced block properties `Configuration Settings`, allowing it to be overwritten on a per block basis using the advanced `Configuration Settings` block property of the {{< ahref path="Cortex.Reference.Blocks.Ssh.ExecuteSshCommand.ExecuteSshCommandBlock.ConfigurationSettings" version="2025.7" title="SSH" >}}.
115
+
<!-- TODO - Documentation - Raise PBI related to SSH block Configuration Settings field -->
116
+
`StrictResponseMatching` can be set to `false`, allowing to match any response text before the `terminalPrompt`. Default is `true`.
##### Added support for user to provide a log path on Log Event blocks
124
+
##### Added support for response grace period in Execute SSH Command Block
119
125
120
-
The [Log Event Block][] has been updated to allow the user to provide a path to log to, on the per block basis.
126
+
The [Execute SSH Command Block][] has been updated to allow for a `ResponseGracePeriod` to be set, which is the number of milliseconds to wait after receiving a matching response and `terminalPrompt`, before assigning the response to the block output variable and continuing the flow.
127
+
This is useful in cases where a device is returning the response in batches and one of the batches matches the expected response and `terminalPrompt`, but the full response has not yet been received from the device.
121
128
122
129
{{% alert title="Note" %}}
130
+
The `ResponseGracePeriod` option can now be added in the advanced block properties `Configuration Settings`, allowing it to be overwritten on a per block basis using the advanced `Configuration Settings` block property of the {{< ahref path="Cortex.Reference.Blocks.Ssh.ExecuteSshCommand.ExecuteSshCommandBlock.ConfigurationSettings" version="2025.7" title="SSH" >}}.
131
+
<!-- TODO - Make describe response grade period feature similar to above -->
132
+
`ResponseGracePeriod` can be set to any number, which is the number of milliseconds to wait for a response before checking the response. Default is `0`.
##### Added support for custom log path on Log Event blocks
141
+
142
+
The [Log Event Block][] has been updated to allow the developer to provide a custom log path where it should write its log to. This is configurable on a per block basis.
123
143
The advanced `Event Log Path` block property allows to specify the path to log to, which is used instead of the default path.
124
-
By default, the property is empty, allowing the log to be written to the default path in configured the execution service's AppSettings.
125
-
<!-- TODO - See whether this is too much, or needs docs -->
126
-
Supported paths format are:
127
-
128
-
* Absolute paths, e.g. `C:\Logs\MyLog.log`
129
-
* Relative paths, e.g. `.\Logs\MyLog.log` (relative to the Execution Service `work` directory)
130
-
* Remote UNC paths, e.g. `\\server\c$\Logs\MyLog.log` (requires `Run As` property to also be configured)
131
-
* Remote Share paths, e.g. `\\server\myshare\Logs\MyLog.log` (requires `Run As` property to also be configured)
144
+
By default, the property is empty, allowing the log to be written to the default path configured in the Execution Service's AppSettings.
145
+
146
+
{{% alert title="Note" %}}
147
+
<!-- TODO - Documentation - Raise PBI related to Event Log Path property -->
148
+
Supported path formats are:
149
+
150
+
* Local Absolute paths, e.g. `C:\Logs\MyLog.log`
151
+
* Local Relative paths, e.g. `.\Logs\MyLog.log` (relative to the Execution Service `work` directory)
152
+
* Remote UNC paths, e.g. `\\server\c$\Logs\MyLog.log` (requires `Run As` property to also be configured with a `LogonType` as `NewCredentials`)
153
+
* Remote Share paths, e.g. `\\server\myshare\Logs\MyLog.log` (requires `Run As` property to also be configured with a `LogonType` as `NewCredentials`)
132
154
{{% /alert %}}
133
155
134
156
Affected Components:
135
157
136
158
<!-- Add support for log path for specific block -->
137
159
<!-- 36224 Log Event Block - Allow user to provide a path to log to for specified block -->
138
160
139
-
##### Added support for stopping multiple executions
161
+
##### Added support for stopping multiple running executions
140
162
141
-
The executions in the [Running Executions][] grid, which can be found in the [Operations Overview][] and [Packages][]sections of the [{{% ctx %}} Gateway][Gateway], has been updated to allow the user to select multiple executions, and stop them at once.
163
+
The executions in the [Running Executions][] grid, which can be found in the [Packages][]page of [{{% ctx %}} Gateway][Gateway], has been updated to allow the administrator to select multiple executions, and stop them at once.
142
164
143
165
{{% alert title="Note" %}}
144
166
Executions can be selected using the `Shift` and `Ctrl` keys.
@@ -151,9 +173,9 @@ Affected Components:
151
173
152
174
#### Performance
153
175
154
-
##### Batched stopping executions
176
+
##### Improved performance of stopping multiple running executions
155
177
156
-
The platform has been updated to optimise the stopping of multiple executions allowing making a single request from [{{% ctx %}} Gateway][Gateway] up to to the [{{% ctx %}} Execution Management Service][], instead of making a request for each execution.
178
+
The {{% ctx %}} Platform has been updated to optimise the stopping of multiple executions using batch requests downstream from [{{% ctx %}} Gateway][Gateway], instead of making individual requests for each execution.
157
179
158
180
Affected Components:
159
181
@@ -164,7 +186,7 @@ Affected Components:
164
186
165
187
##### Improved performance of monitoring service
166
188
167
-
The [{{% ctx %}} Execution Service][] have been updated to improve the performance of the service by batching execution updates to the [{{% ctx %}} Monitoring Service][], rather than sending each update individually.
189
+
The {{% ctx %}} Platform has been updated to optimise the performance of the [{{% ctx %}} Monitoring Service][]by batching execution updates from the [{{% ctx %}} Execution Service][] rather than sending each update individually. This reduces the number of messages sent to the [{{% ctx %}} Monitoring Service][] and improves overall performance.
168
190
169
191
Affected Components:
170
192
@@ -173,13 +195,13 @@ Affected Components:
173
195
174
196
#### Observability
175
197
176
-
##### Migrated from Promptail to Alloy
198
+
##### Migrated from Promtail to Grafana Alloy
177
199
178
-
The [{{% ctx %}} Observability][] has been updated to use [Alloy][] instead of [Promtail][]. [Promptail][] has been deprecated as of 13 of February 2025, entering Long-Term Support on the same date.
200
+
[{{% ctx %}} Observability][] has been updated to use [Grafana Alloy][] instead of [Promtail][] for ingesting logs to [Grafana Loki][]. This is due to [Promtail][] having been deprecated and marked as end-of-life on the 2nd of March 2026.
179
201
180
202
{{% alert title="Note" %}}
181
-
There is currently not documentation on how to migrate from `Promptail` to `Alloy`.
182
-
For further assistance, please raise a case in the {{< ahref path="Cortex.ServicePortal.MainDoc" version="2025.7" title="{{% ctx %}} Service Portal" >}}.
203
+
There is currently not documentation on how to migrate from `Promptail` to `Grafana Alloy`. This will be added in `2025.9`.
204
+
In the meantime, for further assistance, please raise a case in the {{< ahref path="Cortex.ServicePortal.MainDoc" version="2025.7" title="{{% ctx %}} Service Portal" >}}.
183
205
{{% /alert %}}
184
206
185
207
Affected Components:
@@ -209,53 +231,13 @@ Documentation has been updated to point to the [Flow Editor][User Guide - Flow E
209
231
210
232
##### TypeOfFlow not being preserved during upgrade
211
233
212
-
The upgrader has been updated to preserve the `TypeOfFlow` property when upgrading flows. If no `TypeOfFlow` is set, it will default to `Flow`.
234
+
The `{{% ctx%}} Flows Upgrader` has been updated to preserve the `TypeOfFlow` property when upgrading flows. If no `TypeOfFlow` is set, it will default to `Flow`.
213
235
214
236
Affected Components:
215
237
216
238
<!-- Improve upgrade to add TypeOfFlow -->
217
239
<!-- 21997 Process Design & Execution - Upgrader needs to preserve typeofflow -->
218
240
219
-
<!-- ------------------ NOT DOCUMENTED ------------------ -->
220
-
221
-
<!-- INTERNAL -->
222
-
<!-- 35478 Observability - Fix issue with Local Loki user -->
223
-
224
-
<!-- UNDER FEATURE FLAG/NOT RELEASE -->
225
-
<!-- 36502 Patch Upgrade Testing - v2025.3 to v2025.3-Patch -->
0 commit comments