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
@@ -19,6 +19,11 @@ Installation artefacts can be requested by raising a case in the [{{% ctx %}} Se
19
19
20
20
2025.7 is the next [Fast Track][] release of {{% ctx %}} and improves on the [2025.3][] release in the following areas:
21
21
22
+
* Capability
23
+
* Performance
24
+
* Observability
25
+
* Documentation
26
+
22
27
<!-- TBC -->
23
28
24
29
### Components
@@ -61,47 +66,161 @@ Installation artefacts can be requested by raising a case in the [{{% ctx %}} Se
61
66
62
67
### Features
63
68
64
-
<!-- Multi-select -->
65
-
<!-- 36273 API Gateway Service - gateway backend makes single http request to api gateway when stopping multiple executions -->
66
-
<!-- 36196 CORTEX Gateway - make client use single request to backend for stopping multiple executions -->
67
-
<!-- 18138 Platform Visibility - Package Management - User can stop running executions - multi row selection -->
68
-
<!-- 36488 Execution Management Service - Batch stop executions with single message to each execution service -->
69
+
#### Capability
70
+
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:
76
+
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.
81
+
82
+
Affected Components:
69
83
70
84
<!-- MIBs work -->
71
85
<!-- 36085 CORTEX Gateway - Load Mibs - On Startup of Gateway -->
<!-- 35992 Trigger Service - Refactor Mib Node Structure -->
75
-
<!-- 37008 Trigger Service - Add Mib Node Store - Batch Transactions to Improve Performance -->
89
+
<!--37008 Trigger Service - Add Mib Node Store - Batch Transactions to Improve Performance -->
76
90
<!-- 35662 Trigger Service - Replicate Mib Nodes to all partitions -->
77
91
92
+
##### Added ReceivedAt to trap details
93
+
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`.
95
+
96
+
Affected Components:
97
+
78
98
<!-- Add field to trap details -->
79
99
<!-- 36323 Trigger Service - Add ReceivedAt to trap details -->
80
100
101
+
##### Added support for non-printable characters in SSH block
102
+
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.
105
+
106
+
{{% 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`.
##### Added support for user to provide a log path on Log Event blocks
119
+
120
+
The [Log Event Block][] has been updated to allow the user to provide a path to log to, on the per block basis.
121
+
122
+
{{% alert title="Note" %}}
123
+
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)
132
+
{{% /alert %}}
133
+
134
+
Affected Components:
135
+
84
136
<!-- Add support for log path for specific block -->
85
137
<!-- 36224 Log Event Block - Allow user to provide a path to log to for specified block -->
86
138
139
+
##### Added support for stopping multiple executions
140
+
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.
142
+
143
+
{{% alert title="Note" %}}
144
+
Executions can be selected using the `Shift` and `Ctrl` keys.
145
+
{{% /alert %}}
146
+
147
+
Affected Components:
148
+
149
+
<!-- Multi-select -->
150
+
<!-- 18138 Platform Visibility - Package Management - User can stop running executions - multi row selection -->
151
+
152
+
#### Performance
153
+
154
+
##### Batched stopping executions
155
+
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.
157
+
158
+
Affected Components:
159
+
160
+
<!-- Multi-select -->
161
+
<!-- 36273 API Gateway Service - gateway backend makes single http request to api gateway when stopping multiple executions -->
162
+
<!-- 36196 CORTEX Gateway - make client use single request to backend for stopping multiple executions -->
163
+
<!-- 36488 Execution Management Service - Batch stop executions with single message to each execution service -->
164
+
165
+
##### Improved performance of monitoring service
166
+
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.
168
+
169
+
Affected Components:
170
+
87
171
<!-- Improve performance of monitoring service -->
88
172
<!-- 33242 Monitoring Service - Improve performance by batching execution updates -->
89
173
174
+
#### Observability
175
+
176
+
##### Migrated from Promptail to Alloy
177
+
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.
179
+
180
+
{{% 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" >}}.
183
+
{{% /alert %}}
184
+
185
+
Affected Components:
186
+
90
187
<!-- Migrate to Alloy -->
91
-
<!-- 35478 Observability - Fix issue with Local Loki user -->
92
-
<!-- 36133 Observability - Loki URL needs to changing to not have hardcoded username and password in plain text -->
188
+
<!-- 36133 Observability - Loki URL needs to changing to not have hardcoded username and password in plain text - SHOULD NOT DOCUMENT -->
@@ -137,8 +256,6 @@ Installation artefacts can be requested by raising a case in the [{{% ctx %}} Se
137
256
<!-- 35759 Upgrade - IISReset needs to be more specific for dual sites - PATCH 2025.3.{TODO: Patch Version} -->
138
257
<!-- 37028 Upgrade - Upgrade Fails if run again after roll back - TODO Patch 2025.3.25342 -->
139
258
140
-
### Bug Fixes
141
-
142
259
### Deprecated Features
143
260
144
261
There are no features deprecated as part of the 2025.7 release of the {{% ctx %}} Platform.
@@ -337,8 +454,9 @@ Releases are currently forecast to be made available on:
337
454
[Adding Innovation to a 7.2 Installation - Single Server - Without HA]: {{< url path="Cortex.GettingStarted.OnPremise.AddInnovationTo72.SingleServerWithoutHA.MainDoc" version="2025.7" >}}
338
455
[Adding Innovation to a 7.2 Installation - Multiple Server - With HA]: {{< url path="Cortex.GettingStarted.OnPremise.AddInnovationTo72.MultipleServerWithHA.MainDoc" version="2025.7" >}}
339
456
340
-
[Upgrade - Single Server - Without HA]: {{< url path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025.3to2025.7.SingleServerWithoutHA.MainDoc" version="2025.7" >}}
341
-
[Upgrade - Multiple Server - With HA]: {{< url path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025.3to2025.7.MultipleServerWithHA.MainDoc" version="2025.7" >}}
457
+
<!-- TODO - Update to 2025.7 -->
458
+
[Upgrade - Single Server - Without HA]: {{< url path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025.3to2025.5.SingleServerWithoutHA.MainDoc" version="2025.7" >}}
459
+
[Upgrade - Multiple Server - With HA]: {{< url path="Cortex.Guides.UpgradeGuides.UpgradeCortex.2025.3to2025.5.MultipleServerWithHA.MainDoc" version="2025.7" >}}
342
460
[Breaking - Introduced Code Analyser to the {{% ctx %}} Execution Service]: {{< ref "#introduced-code-analyser-to-the-cortex-execution-service-1" >}}
343
461
344
462
[{{% ctx %}} Service Portal]: {{< url path="Cortex.ServicePortal.MainDoc" version="2025.7" >}}
0 commit comments