You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For audit compliance reasons, we'd like to keep a subset of our logs for an extended period of time. We can't set the retention-period config globally, as all logs would be stored for this period, and we'd run out of disk space very quickly. Currently, the charm docs say: Specifying retention periods for individual streams is not currently supported..
Seem like the requirer side could expose retention period as a config option and the loki libs would render a stream selector with the requirer's juju topology.
This is still a bit risky because the requirer charm could technically provide a selector that would match other streams unintentionally.
On the provider side (loki itself) we will be able to render the selector ourselves only if we add to reldata an analogue of scrape_metadata, because CMRs are obfuscated.
We need to take loki-coordinator-k8s into account as well!
Enhancement Proposal
For audit compliance reasons, we'd like to keep a subset of our logs for an extended period of time. We can't set the
retention-period
config globally, as all logs would be stored for this period, and we'd run out of disk space very quickly. Currently, the charm docs say:Specifying retention periods for individual streams is not currently supported.
.This feature is supported by compactor using the
retention_stream
configuration: https://grafana.com/docs/loki/latest/operations/storage/retention/#retention-configurationThe text was updated successfully, but these errors were encountered: