Configure the number of retries sending data if an error occurs

When you deploy or upgrade the Logging agent, you can configure the logs-values.yaml file to set retryLimit and indicate whether the agent should retry sending the data to an IBM Cloud Logs instance.

After you modify the logs-values.yaml, you can Upgrade the agent or continue modifying the file before applying all the changes.

Valid values are:

• false to indicate that there is no limit for the number of retries that the scheduler can do. This is the default value.

  The entry in the logs-values.yaml file looks as follows:

  retryLimit: false
  

• An integer N value greater or equal to 1.

  The entry in the logs-values.yaml file looks as follows:

  retryLimit: 8
  

• no_retries to indicate that data is not sent to the destination if it failed the first time.

  The entry in the logs-values.yaml file looks as follows:

  retryLimit: "no_retries"
  

For more information, see the Fluentbit documentation about retries to understand the implications of setting this value.

In some situations, this setting could lead to log data being discarded by the agent due to the inability to send.