OBSDOCS-1972 migrate old content - add in performance_reliability folder

Author: gabriel-rh

_topic_maps/_topic_map.yml

@@ -98,3 +98,13 @@ Topics:
   File: default-logging-alerts
 - Name: Custom logging alerts
   File: custom-logging-alerts
+---
+Name: Performance and reliability tuning
+Dir: performance_reliability
+Topics:
+- Name: Flow control mechanisms
+  File: logging-flow-control-mechanisms
+- Name: Filtering logs by content
+  File: logging-content-filtering
+- Name: Filtering logs by metadata
+  File: logging-input-spec-filtering

performance_reliability/_attributes

@@ -0,0 +1 @@
+../_attributes/

performance_reliability/images

@@ -0,0 +1 @@
+../images/

performance_reliability/logging-content-filtering.adoc

@@ -0,0 +1,29 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="logging-content-filtering"]
+= Filtering logs by content
+:context: logging-content-filtering
+
+toc::[]
+
+Collecting all logs from a cluster might produce a large amount of data, which can be expensive to transport and store.
+
+You can reduce the volume of your log data by filtering out low priority data that does not need to be stored. {logging-uc} provides content filters that you can use to reduce the volume of log data.
+
+[NOTE]
+====
+Content filters are distinct from `input` selectors. `input` selectors select or ignore entire log streams based on source metadata. Content filters edit log streams to remove and modify records based on the record content.
+====
+
+Log data volume can be reduced by using one of the following methods:
+
+* xref:../performance_reliability/logging-content-filtering.adoc#logging-content-filter-drop-records_logging-content-filtering[Configuring content filters to drop unwanted log records]
+* xref:../performance_reliability/logging-content-filtering.adoc#logging-content-filter-prune-records_logging-content-filtering[Configuring content filters to prune log records]
+
+include::modules/logging-content-filter-drop-records.adoc[leveloffset=+1]
+include::modules/logging-content-filter-prune-records.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources_logging-content-filtering"]
+== Additional resources
+* xref:../log_collection_forwarding/configuring-log-forwarding.adoc#cluster-logging-collector-log-forwarding-about_configuring-log-forwarding[About forwarding logs to third-party systems]

performance_reliability/logging-flow-control-mechanisms.adoc

@@ -0,0 +1,43 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="logging-flow-control-mechanisms"]
+= Flow control mechanisms
+:context: logging-flow-control-mechanisms
+
+toc::[]
+
+If logs are produced faster than they can be collected, it can be difficult to predict or control the volume of logs being sent to an output.
+Not being able to predict or control the volume of logs being sent to an output can result in logs being lost. If there is a system outage and log buffers are accumulated without user control, this can also cause long recovery times and high latency when the connection is restored.
+
+As an administrator, you can limit logging rates by configuring flow control mechanisms for your {logging}.
+
+[id="logging-configuring-flow-control-benefits"]
+== Benefits of flow control mechanisms
+
+* The cost and volume of logging can be predicted more accurately in advance.
+* Noisy containers cannot produce unbounded log traffic that drowns out other containers.
+* Ignoring low-value logs reduces the load on the logging infrastructure.
+* High-value logs can be preferred over low-value logs by assigning higher rate limits.
+
+[id="logging-configuring-flow-control-about-rate-limits"]
+== Configuring rate limits
+
+Rate limits are configured per collector, which means that the maximum rate of log collection is the number of collector instances multiplied by the rate limit.
+
+Because logs are collected from each node's file system, a collector is deployed on each cluster node. For example, in a 3-node cluster, with a maximum rate limit of 10 records per second per collector, the maximum rate of log collection is 30 records per second.
+
+Because the exact byte size of a record as written to an output can vary due to transformations, different encodings, or other factors, rate limits are set in number of records instead of bytes.
+
+You can configure rate limits in the `ClusterLogForwarder` custom resource (CR) in two ways:
+
+Output rate limit:: Limit the rate of outbound logs to selected outputs, for example, to match the network or storage capacity of an output. The output rate limit controls the aggregated per-output rate.
+
+Input rate limit:: Limit the per-container rate of log collection for selected containers.
+
+include::modules/logging-set-output-rate-limit.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../log_collection_forwarding/logging-output-types.adoc#logging-output-types[Log output types]
+
+include::modules/logging-set-input-rate-limit.adoc[leveloffset=+1]

performance_reliability/logging-input-spec-filtering.adoc

@@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="logging-input-spec-filtering"]
+= Filtering logs by metadata
+:context: logging-input-spec-filtering
+
+toc::[]
+
+
+You can filter logs in the `ClusterLogForwarder` CR to select or ignore an entire log stream based on the metadata by using the `input` selector. As an administrator or developer, you can include or exclude the log collection to reduce the memory and CPU load on the collector.
+
+[IMPORTANT]
+====
+You can use this feature only if the Vector collector is set up in your logging deployment.
+====
+
+[NOTE]
+====
+`input` spec filtering is different from content filtering. `input` selectors select or ignore entire log streams based on the source metadata. Content filters edit the log streams to remove and modify the records based on the record content.
+====
+
+include::modules/logging-input-spec-filter-namespace-container.adoc[leveloffset=+1]
+include::modules/logging-input-spec-filter-labels-expressions.adoc[leveloffset=+1]
+include::modules/logging-input-spec-filter-audit-infrastructure.adoc[leveloffset=+1]

performance_reliability/modules

@@ -0,0 +1 @@
+../modules/

performance_reliability/snippets

@@ -0,0 +1 @@
+../snippets/