Skip to content

Commit e38e64c

Browse files
authored
Merge pull request #3134 from ClickHouse/fix-grammar
Update why_default_logging_verbose.mdx
2 parents 81e4751 + 580597a commit e38e64c

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

knowledgebase/why_default_logging_verbose.mdx

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
date: 2025-01-10
3-
title: Why ClickHouse default logging setting is verbose?
4-
description: "Explain why ClickHouse developers chose to set a verbose log level by default"
3+
title: Why is ClickHouse logging so verbose by default?
4+
description: "Learn why the ClickHouse developers chose to set a verbose logging level by default."
55
tags: ['Settings']
66
keywords: ['Default Logging']
77
---
@@ -11,23 +11,23 @@ keywords: ['Default Logging']
1111

1212
## Verbose Logging
1313

14-
One thing that often confuses new users is that ClickHouse generates a lot of log output, even under light load.
14+
One thing that often confuses new users is that ClickHouse generates a lot of logging output, even under light load.
1515

16-
This is because the default log level is for historical reasons `trace` (instead of `warning` that would be the default in other databases).
16+
This is because the default logging level, due to historical reasons, is `trace` (instead of `warning` that would be the default in other databases).
1717

18-
The ClickHouse developers argue that `trace` provides a lot of insight in case goes wrong.
18+
The ClickHouse developers argue that `trace` provides a lot of insight in case something goes wrong.
1919

20-
On the other hand, large volumes of logging means that system table `system.text_log` fills up quickly and needs to be merged in the background.
20+
On the other hand, large volumes of logging mean that the system table `system.text_log` fills up quickly and needs to be merged in the background.
2121

22-
If the database runs stable, users may re-configure the log level.
22+
If the database runs stably, users may re-configure the log level, which we explain how to do below.
2323

24-
## Change log level
24+
## Change the log level
2525

26-
The different log level available are documented [here](https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#logger)
26+
The different log levels available are documented [here](https://clickhouse.com/docs/en/operations/server-configuration-parameters/settings#logger)
2727

28-
Edit the ClickHouse server configuration file (`/etc/clickhouse-server/config.xml`) to modify the log level.
28+
You'll need to edit the ClickHouse server configuration file (`/etc/clickhouse-server/config.xml`) to modify the log level.
2929

30-
Default value is `trace`, change it to the desired level.
30+
The default value is `trace` but you can change it to the desired level. See the comment below:
3131

3232
```
3333
<clickhouse>
@@ -50,4 +50,4 @@ Default value is `trace`, change it to the desired level.
5050
<level>trace</level>
5151
... Rest of the configuration file
5252
</clickhouse>
53-
```
53+
```

0 commit comments

Comments
 (0)