DOC-14177 Document that it is not possible to “disable a logging channel” (#20158)

* Added log-channel-note.md include file to document that log channels can not be disabled.
* Incorporated Joe’s feedback.
* Copied changes to v24.3, v25.1, v25.2.

Author: florence-crl

src/current/_includes/v24.3/log-channel-note.md

@@ -0,0 +1,3 @@
+{{site.data.alerts.callout_info}}
+Log channels cannot be completely disabled. You can configure [how log messages are routed to different sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks) and [adjust verbosity levels]({% link {{ page.version.version }}/configure-logs.md %}#set-logging-levels), but you cannot turn off a log channel entirely. For example, a channel that **is not explicitly configured** for a [file group]({% link {{ page.version.version }}/configure-logs.md %}#output-to-files) **is enabled** in the `default` file group.
+{{site.data.alerts.end}}

src/current/_includes/v25.1/log-channel-note.md

@@ -0,0 +1,3 @@
+{{site.data.alerts.callout_info}}
+Log channels cannot be completely disabled. You can configure [how log messages are routed to different sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks) and [adjust verbosity levels]({% link {{ page.version.version }}/configure-logs.md %}#set-logging-levels), but you cannot turn off a log channel entirely. For example, a channel that **is not explicitly configured** for a [file group]({% link {{ page.version.version }}/configure-logs.md %}#output-to-files) **is enabled** in the `default` file group.
+{{site.data.alerts.end}}

src/current/_includes/v25.2/log-channel-note.md

@@ -0,0 +1,3 @@
+{{site.data.alerts.callout_info}}
+Log channels cannot be completely disabled. You can configure [how log messages are routed to different sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks) and [adjust verbosity levels]({% link {{ page.version.version }}/configure-logs.md %}#set-logging-levels), but you cannot turn off a log channel entirely. For example, a channel that **is not explicitly configured** for a [file group]({% link {{ page.version.version }}/configure-logs.md %}#output-to-files) **is enabled** in the `default` file group.
+{{site.data.alerts.end}}

src/current/_includes/v25.3/log-channel-note.md

@@ -0,0 +1,3 @@
+{{site.data.alerts.callout_info}}
+Log channels cannot be completely disabled. You can configure [how log messages are routed to different sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks) and [adjust verbosity levels]({% link {{ page.version.version }}/configure-logs.md %}#set-logging-levels), but you cannot turn off a log channel entirely. For example, a channel that **is not explicitly configured** for a [file group]({% link {{ page.version.version }}/configure-logs.md %}#output-to-files) **is enabled** in the `default` file group.
+{{site.data.alerts.end}}

src/current/v24.3/configure-logs.md

@@ -293,6 +293,8 @@ By default, `cockroach start` and `cockroach start-single-node` do not print any
 
 ### Logging channel selection
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 For each sink, multiple channels can be selected. Note that:
 
 - Spacing between items will vary according to the syntax used.

src/current/v24.3/logging-overview.md

@@ -22,6 +22,8 @@ All [`cockroach` commands]({% link {{ page.version.version }}/cockroach-commands
 
 ## Logging channels
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 Log messages in CockroachDB are directed into logging channels, which can in turn be assigned to output to one or more [log sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks).
 
 This allows you to group channels that log related information (e.g., operational, security, or SQL events) into their own sinks. Each sink can output to a predetermined destination where the logs can be collected and parsed. For usage examples, see [Logging Use Cases]({% link {{ page.version.version }}/logging-use-cases.md %}).

src/current/v25.1/configure-logs.md

@@ -293,6 +293,8 @@ By default, `cockroach start` and `cockroach start-single-node` do not print any
 
 ### Logging channel selection
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 For each sink, multiple channels can be selected. Note that:
 
 - Spacing between items will vary according to the syntax used.

src/current/v25.1/logging-overview.md

@@ -22,6 +22,8 @@ All [`cockroach` commands]({% link {{ page.version.version }}/cockroach-commands
 
 ## Logging channels
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 Log messages in CockroachDB are directed into logging channels, which can in turn be assigned to output to one or more [log sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks).
 
 This allows you to group channels that log related information (e.g., operational, security, or SQL events) into their own sinks. Each sink can output to a predetermined destination where the logs can be collected and parsed. For usage examples, see [Logging Use Cases]({% link {{ page.version.version }}/logging-use-cases.md %}).

src/current/v25.2/configure-logs.md

@@ -293,6 +293,8 @@ By default, `cockroach start` and `cockroach start-single-node` do not print any
 
 ### Logging channel selection
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 For each sink, multiple channels can be selected. Note that:
 
 - Spacing between items will vary according to the syntax used.

src/current/v25.2/logging-overview.md

@@ -22,6 +22,8 @@ All [`cockroach` commands]({% link {{ page.version.version }}/cockroach-commands
 
 ## Logging channels
 
+{% include {{ page.version.version }}/log-channel-note.md %}
+
 Log messages in CockroachDB are directed into logging channels, which can in turn be assigned to output to one or more [log sinks]({% link {{ page.version.version }}/configure-logs.md %}#configure-log-sinks).
 
 This allows you to group channels that log related information (e.g., operational, security, or SQL events) into their own sinks. Each sink can output to a predetermined destination where the logs can be collected and parsed. For usage examples, see [Logging Use Cases]({% link {{ page.version.version }}/logging-use-cases.md %}).