Skip to content

Commit 9dc037a

Browse files
author
Donna-Marie Smith
committed
additional casing issues
1 parent 4a617a3 commit 9dc037a

3 files changed

Lines changed: 21 additions & 21 deletions

File tree

  • content/en/docs
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
2-
title: "How do I change the logging level?"
3-
linkTitle: "How do I change the logging level?"
4-
description: "Instructions on how to change the {{% ctx %}} logging level."
2+
title: "How do I change the Logging Level?"
3+
linkTitle: "How do I change the Logging Level?"
4+
description: "Instructions on how to change the {{% ctx %}} Logging Level."
55
weight: 1000
66
---
77

88
{{% 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.
99

1010
{{% alert title="Note" %}}
11-
Although the logging level for the {{% ctx %}} API Gateway service can be increased, it will still always log all API calls received regardless of logging level.
11+
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.
1212
{{% / alert %}}
1313

14-
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.
14+
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.
1515

16-
Whilst increased logging levels are in place, we would recommend closely monitoring system performance and disk space usage.
16+
Whilst increased Logging Levels are in place, we would recommend closely monitoring system performance and disk space usage.
1717

18-
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.
18+
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.
1919

2020
[Postman]: {{< url path="Postman.Downloads.MainDoc" >}}
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
2-
title: "How do I change the logging level?"
3-
linkTitle: "How do I change the logging level?"
4-
description: "Instructions on how to change the {{% ctx %}} logging level."
2+
title: "How do I change the Logging Level?"
3+
linkTitle: "How do I change the Logging Level?"
4+
description: "Instructions on how to change the {{% ctx %}} Logging Level."
55
weight: 1000
66
---
77

88
{{% 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.
99

1010
{{% alert title="Note" %}}
11-
Although the logging level for the {{% ctx %}} API Gateway service can be increased, it will still always log all API calls received regardless of logging level.
11+
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.
1212
{{% / alert %}}
1313

14-
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.
14+
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.
1515

16-
Whilst increased logging levels are in place, we would recommend closely monitoring system performance and disk space usage.
16+
Whilst increased Logging Levels are in place, we would recommend closely monitoring system performance and disk space usage.
1717

18-
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.
18+
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.
1919

2020
[Postman]: {{< url path="Postman.Downloads.MainDoc" >}}
Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
2-
title: "How do I change the logging level?"
3-
linkTitle: "How do I change the logging level?"
4-
description: "Instructions on how to change the {{% ctx %}} logging level."
2+
title: "How do I change the Logging Level?"
3+
linkTitle: "How do I change the Logging Level?"
4+
description: "Instructions on how to change the {{% ctx %}} Logging Level."
55
weight: 1000
66
---
77

88
{{% 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.
99

1010
{{% alert title="Note" %}}
11-
Although the logging level for the {{% ctx %}} API Gateway service can be increased, it will still always log all API calls received regardless of logging level.
11+
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.
1212
{{% / alert %}}
1313

14-
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.
14+
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.
1515

16-
Whilst increased logging levels are in place, we would recommend closely monitoring system performance and disk space usage.
16+
Whilst increased Logging Levels are in place, we would recommend closely monitoring system performance and disk space usage.
1717

18-
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.
18+
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.
1919

2020
[Postman]: {{< url path="Postman.Downloads.MainDoc" >}}

0 commit comments

Comments
 (0)