Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
bc32d82
Added initial content for 2025.11
Nov 18, 2025
8bc7358
added steps for configuring Loki Retention Period (#247)
Cortex-DMS Nov 26, 2025
6109d51
Flow Editor User Guide Updates (#249)
Cortex-DMS Dec 8, 2025
8e4f318
Feature/add running execution documentation changes to 2025.11 (#251)
Cortex-DMS Dec 11, 2025
f883288
Feature/add authentication and authorisation documentation to 2025.11…
Cortex-DMS Dec 17, 2025
5f8c102
Feature/update setup gateway to include OIDC Setup (#257)
Cortex-DMS Mar 10, 2026
3c2844b
Merge main into 2026.3 (#261)
Cortex-DMS Mar 19, 2026
0d75cd3
Feature/update variable editor documentation (#263)
Cortex-DMS Mar 23, 2026
fa68f90
Remove non-supported versions of documentation
cortex-lp Mar 24, 2026
7a71cc2
Merge main into 2026.3 to fix links
cortex-lp Mar 25, 2026
eeb4d25
Update 2026.3 documentation to reflect latest patch (#269)
cortex-lp Mar 30, 2026
b17f830
Update package version editor user guide to include snmp trap details…
Cortex-DMS Apr 1, 2026
08dae99
Added robos.txt configuration instructions for CORTEX Configuration P…
cortex-sr Apr 20, 2026
544734a
Feature/observability upgrade components (#273)
Cortex-DMS Apr 22, 2026
a3bb6ac
Upgrade guides to 2026.3
cortex-lp Apr 27, 2026
a02c3bf
Merge main into 2026.3
cortex-lp Apr 28, 2026
8afd438
Release/2026.3/release notes whats new (#277)
cortex-lp May 7, 2026
78ac8ac
Fix merge conflicts for release (#279)
cortex-lp May 7, 2026
be6dc05
Merge remote-tracking branch 'origin/main' into 2026.3
May 7, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
1 change: 1 addition & 0 deletions .htmltest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ IgnoreURLs:
- "https://scribehow.com/.*"
- "https://www.rabbitmq.com/.*"
- "https://letsencrypt.org/.*"
- "https://support.microsoft.com/.*"
IgnoreDirs:
- "docs/?.*/_print/"
- "docs/?.*/_shared/"
Expand Down
10 changes: 8 additions & 2 deletions config/_default/config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -203,16 +203,22 @@ enable = true
[[menu.main]]
identifier = 'documentation'
name = 'Documentation'
url = '/docs/2025.9'
url = '/docs/2026.3'
weight = 10

# Releases menu
[[params.versions]]
version = "2026.3"
url = "/docs/2026.3/"
dotNetVersion = "net-8.0"
inSupport = true
latest = true

[[params.versions]]
version = "2025.9"
url = "/docs/2025.9/"
dotNetVersion = "net-8.0"
inSupport = true
latest = true

[[params.versions]]
version = "2025.3"
Expand Down
44 changes: 1 addition & 43 deletions content/en/blog/releases/2025.X/2025.9/2025.9.26161.md

Large diffs are not rendered by default.

1,321 changes: 1,321 additions & 0 deletions content/en/blog/releases/2026.X/2026.3.md

Large diffs are not rendered by default.

20 changes: 20 additions & 0 deletions content/en/docs/2025.3/FAQs/change-logging-levels/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: "How do I change the Logging Level?"
linkTitle: "How do I change the Logging Level?"
description: "Instructions on how to change the {{% ctx %}} Logging Level."
weight: 1000
---

{{% ctx %}} Logging Levels are set to `Error` by default for most services. However, levels can be changed whilst {{% ctx %}} is running by sending REST calls to the {{% ctx %}} API Gateway service.

{{% alert title="Note" %}}
Although the Logging Level for the {{% ctx %}} API Gateway service can be increased, it will still always log all API calls regardless of Logging Level configured.
{{% / alert %}}

If increasing the Logging Level, particularly if increasing for everything or for Block Logging, we recommend that this is done only when required. Increasing log levels will lead to an increase in disk usage and disk writes, which can impact the performance of the {{% ctx %}} platform if not monitored.

Whilst increased Logging Levels are in place, we would recommend closely monitoring system performance and disk space usage.

All REST calls to update Logging Levels use Basic Auth and can be made using REST clients such as [Postman][] or using scripts such as PowerShell.

[Postman]: {{< url path="Postman.Downloads.MainDoc" >}}
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Change All Logging Levels"
linkTitle: "Change All Logging Levels"
description: "Instructions on how to change the Logging Level for All Logging."
weight: 10
---

# {{% param title %}}

To change the Logging Level for all services, the below PowerShell script can be used to make a REST call against your {{% ctx %}} platform.

1. Run Windows PowerShell ISE as Administrator.
1. Copy the following script into the PowerShell window:

``` powershell
$serverFQDN = "server.domain.com"
$APIGatewayPort = 8722
$loglevel = 4
$user = "BasicAuthUser"

$securePass = Read-Host -Prompt "Enter password for $user" -AsSecureString

$ptr = [Runtime.InteropServices.Marshal]::SecureStringToBSTR($securePass)
try {
$plainPass = [Runtime.InteropServices.Marshal]::PtrToStringBSTR($ptr)

$authBytes = [System.Text.Encoding]::ASCII.GetBytes("$user`:$plainPass")
$base64AuthInfo = [Convert]::ToBase64String($authBytes)
}
finally {
[Runtime.InteropServices.Marshal]::ZeroFreeBSTR($ptr)

$plainPass = $null
Remove-Variable -Name plainPass -Force
}

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Content-Type", "application/json")
$headers.Add("Accept", "application/json")
$headers.Add("Authorization", "Basic $base64AuthInfo")
$path = "applications/logging"
$body = @"
$loglevel
"@

$response = Invoke-RestMethod "https://${serverFQDN}:$APIGatewayPort/api/v1/default/default/$path" -Method PUT -Headers $headers -Body $body
$response
```

1. Configure the following variables:
* `$serverFQDN` – The fully qualified domain name for the Application Server or Load Balancer
* `$APIGatewayPort` – {{% ctx %}} API Gateway Service Port (8722) or Load Balancer port (typically 443 or 8722)
* `$loglevel` – Desired log level as an integer, `1` is enabled and `4` is the default error level
* `$user` – {{% ctx %}} API Gateway Basic Auth Username

1. Execute the script, entering the Basic Auth User's password when prompted.
1. Confirm success response:

If the call was successful, there should be no errors and the following response should be received

``` powershell
LogLevel was successfully configured.
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
---
title: "Change Block Logging Level"
linkTitle: "Change Block Logging Level"
description: "Instructions on how to change the Logging Level for Block Logging."
weight: 5
---

# {{% param title %}}

Block Logging in {{% ctx %}} logs the following Block Properties by default regardless of the log level configured:

* Execute Data Command
* Command > commandText
* Command > parameters
* Execute Http Request
* Http Request
* Http Response
* Execute Soap Request
* Soap Request
* Soap Response
* Execute PowerShell Script
* Script
* Parameters
* Outputs
* Records
* Execute Ssh Command
* Command
* Response
* Ssh Logs

To change the Logging Level for Block Logging so that every block is logged when executed, the below PowerShell script can be used to make a REST call against your {{% ctx %}} platform.

1. Run Windows PowerShell ISE as Administrator.
1. Copy the following script into the PowerShell window:

``` powershell
$serverFQDN = "server.domain.com"
$APIGatewayPort = 8722
$loglevel = 4
$user = "BasicAuthUser"

$securePass = Read-Host -Prompt "Enter password for $user" -AsSecureString

$ptr = [Runtime.InteropServices.Marshal]::SecureStringToBSTR($securePass)
try {
$plainPass = [Runtime.InteropServices.Marshal]::PtrToStringBSTR($ptr)

$authBytes = [System.Text.Encoding]::ASCII.GetBytes("$user`:$plainPass")
$base64AuthInfo = [Convert]::ToBase64String($authBytes)
}
finally {
[Runtime.InteropServices.Marshal]::ZeroFreeBSTR($ptr)

$plainPass = $null
Remove-Variable -Name plainPass -Force
}

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Content-Type", "application/json")
$headers.Add("Accept", "application/json")
$headers.Add("Authorization", "Basic $base64AuthInfo")
$path = "applications/execution/services/engine/blocks/packages/versions/executions/flows/workspaces/blocks/logging"
$body = @"
$loglevel
"@

$response = Invoke-RestMethod "https://${serverFQDN}:$APIGatewayPort/api/v1/default/default/$path" -Method PUT -Headers $headers -Body $body
$response
```

1. Configure the following variables:
* `$serverFQDN` – The fully qualified domain name for the Application Server or Load Balancer
* `$APIGatewayPort` – {{% ctx %}} API Gateway Service Port (8722) or Load Balancer port (typically 443 or 8722)
* `$loglevel` – Desired log level as an integer, `1` is enabled and `4` is the default error level
* `$user` – {{% ctx %}} API Gateway Basic Auth Username

1. Execute the script, entering the Basic Auth User's password when prompted.
1. Confirm success response:

If the call was successful, there should be no errors and the following response should be received

``` powershell
LogLevel was successfully configured.
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Change Flow Logging Level"
linkTitle: "Change Flow Logging Level"
description: "Instructions on how to change the Logging Level for Flow Logging."
weight: 1
---

# {{% param title %}}

To change the Logging Level for Flow Logging, the below PowerShell script can be used to make a REST call against your {{% ctx %}} platform.

1. Run Windows PowerShell ISE as Administrator.
1. Copy the following script into the PowerShell window:

``` powershell
$serverFQDN = "server.domain.com"
$APIGatewayPort = 8722
$loglevel = 4
$user = "BasicAuthUser"

$securePass = Read-Host -Prompt "Enter password for $user" -AsSecureString

$ptr = [Runtime.InteropServices.Marshal]::SecureStringToBSTR($securePass)
try {
$plainPass = [Runtime.InteropServices.Marshal]::PtrToStringBSTR($ptr)

$authBytes = [System.Text.Encoding]::ASCII.GetBytes("$user`:$plainPass")
$base64AuthInfo = [Convert]::ToBase64String($authBytes)
}
finally {
[Runtime.InteropServices.Marshal]::ZeroFreeBSTR($ptr)

$plainPass = $null
Remove-Variable -Name plainPass -Force
}

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Content-Type", "application/json")
$headers.Add("Accept", "application/json")
$headers.Add("Authorization", "Basic $base64AuthInfo")
$path = "applications/execution/services/engine/blocks/packages/versions/executions/flows/logging"
$body = @"
$loglevel
"@

$response = Invoke-RestMethod "https://${serverFQDN}:$APIGatewayPort/api/v1/default/default/$path" -Method PUT -Headers $headers -Body $body
$response
```

1. Configure the following variables:
* `$serverFQDN` – The fully qualified domain name for the Application Server or Load Balancer
* `$APIGatewayPort` – {{% ctx %}} API Gateway Service Port (8722) or Load Balancer port (typically 443 or 8722)
* `$loglevel` – Desired log level as an integer, `1` is enabled and `4` is the default error level
* `$user` – {{% ctx %}} API Gateway Basic Auth Username

1. Execute the script, entering the Basic Auth User's password when prompted.
1. Confirm success response:

If the call was successful, there should be no errors and the following response should be received

``` powershell
LogLevel was successfully configured.
```
Loading
Loading