Skip to content

feat(chart, collectors): option to provide volume for filelog offsets#331

Merged
basti1302 merged 2 commits intomainfrom
add-option-to-use-volume-instead-of-configmap-for-filelog-offset-storage
Apr 7, 2025
Merged

feat(chart, collectors): option to provide volume for filelog offsets#331
basti1302 merged 2 commits intomainfrom
add-option-to-use-volume-instead-of-configmap-for-filelog-offset-storage

Conversation

@basti1302
Copy link
Copy Markdown
Member

Users now optionally can provide a persistent volume for storing filelog
offsets, instead of the default ConfigMap which is limited to 1 MB. The
context of this is the logfile offsets that the filelog receiver stores
so that lines from log files are not emitted multiple times in case the
collector pods are restarted.

Users now optionally can provide a persistent volume for storing filelog
offsets, instead of the default ConfigMap which is limited to 1 MB. The
context of this is the logfile offsets that the filelog receiver stores
so that lines from log files are not emitted multiple times in case the
collector pods are restarted.
In particular, account for resource detection taking some time,
depending on the environment.
@basti1302 basti1302 force-pushed the add-option-to-use-volume-instead-of-configmap-for-filelog-offset-storage branch from c8fa17a to 4c0a661 Compare April 7, 2025 21:11
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 7, 2025

@basti1302 basti1302 merged commit 0539d6b into main Apr 7, 2025
11 checks passed
@basti1302 basti1302 deleted the add-option-to-use-volume-instead-of-configmap-for-filelog-offset-storage branch April 7, 2025 21:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant