From 366de5e230df0ebd7eee3ef7de9109aa52f4918a Mon Sep 17 00:00:00 2001 From: Jannik Brand Date: Mon, 19 Aug 2024 11:21:43 +0200 Subject: [PATCH] Add Fluent Bit retry configuration By default Fluent Bit [uses](https://docs.fluentbit.io/manual/administration/scheduling-and-retries#configuring-retries) a Retry_Limit of 1. Since senders want to ensure that telemetry data is ingested, even if the observability backend (e.g. SAP Cloud Logging) is temporarily unavailable (e.g. due to network problems), we should recommend at least 3 retries. --- docs/ingest-via-json-api-endpoint-3416f8f.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/ingest-via-json-api-endpoint-3416f8f.md b/docs/ingest-via-json-api-endpoint-3416f8f.md index a1c701b..f6b2544 100644 --- a/docs/ingest-via-json-api-endpoint-3416f8f.md +++ b/docs/ingest-via-json-api-endpoint-3416f8f.md @@ -23,7 +23,8 @@ You can use arbitrary log shippers to send to the mTLS ingest JSON API endpoint. tls true Compress gzip URI / - Format json + Format json + Retry_Limit 3 ```