remove unnecessary attribute

openshift · Sep 1, 2023 · bf48536 · bf48536
1 parent 4f60a27
commit bf48536
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/_attributes/common-attributes.adoc b/_attributes/common-attributes.adoc
@@ -131,7 +131,6 @@ endif::[]
 :logging-title-uc: Logging subsystem for Red Hat OpenShift
 :logging: logging subsystem
 :logging-uc: Logging subsystem
-:ocp-logging: OpenShift Logging
 //serverless
 :ServerlessProductName: OpenShift Serverless
 :ServerlessProductShortName: Serverless

diff --git a/modules/loki-rate-limit-errors.adoc b/modules/loki-rate-limit-errors.adoc
@@ -8,7 +8,7 @@
 
 If the Log Forwarder API forwards a large block of messages that exceeds the rate limit to Loki, Loki generates rate limit (`429`) errors.
 
-These errors can occur during normal operation. For example, when adding {ocp-logging} to a cluster that already has some logs, rate limit errors might occur while {ocp-logging} tries to ingest all of the existing log entries. In this case, if the rate of addition of new logs is less than the total rate limit, the historical data is eventually ingested, and the rate limit errors are resolved without requiring user intervention.
+These errors can occur during normal operation. For example, when adding the {logging} to a cluster that already has some logs, rate limit errors might occur while the {logging} tries to ingest all of the existing log entries. In this case, if the rate of addition of new logs is less than the total rate limit, the historical data is eventually ingested, and the rate limit errors are resolved without requiring user intervention.
 
 In cases where the rate limit errors continue to occur, you can fix the issue by modifying the `LokiStack` custom resource (CR).
 
@@ -33,7 +33,7 @@ The `LokiStack` CR is not available on Grafana-hosted Loki. This topic does not
 \"received_at\":\"2021-08-31T11:46:32.800278+00:00\",\"version\":\"1.7.4 1.6.0\"}},\"@timestamp\":\"2021-08-31T11:46:32.799692+00:00\",\"viaq_index_name\":\"audit-write\",\"viaq_msg_id\":\"MzFjYjJkZjItNjY0MC00YWU4LWIwMTEtNGNmM2E5ZmViMGU4\",\"log_type\":\"audit\"}"]]}]}
 ----
 
-* After you enter `oc logs -n openshift-logging -l component=collector`, the collector logs in your {ocp-logging} cluster show a line containing one of the following error messages:
+* After you enter `oc logs -n openshift-logging -l component=collector`, the collector logs in your cluster show a line containing one of the following error messages:
 +
 [source,text]
 ----