Kaviraj Kanagaraj

Adding one more entry to the Issue description. /cc @cstyan > make -config.expand-env=true as default in promtail. Rationale being good default experience for promtail to understand ENV in it's config....

@aksonlyaks thanks for reporting the issue. > I feel chunk folder should also be present to store past logs I quickly checked in one of our internal AWS setup. and...

So looks like chunks are getting flushed just fine. May I know what query you using it for that dashboard?

@aksonlyaks this is the config that we use internally and that is working with latest loki version. ``` storage_config: aws: region: # e.g: us-east-2 s3: s3:// s3forcepathstyle: false boltdb_shipper: active_index_directory:...

@aksonlyaks from the logs you shared, looks like loki couldn't find the right bucket to flush the chunks. If chunks are not flushed then you can query logs only from...

I'm investigating! you can even reproduce by directly start any container with loki logger and some unreachable loki-url, 1. with `local` log driver ``` docker run --log-driver local --log-opt max-size=10m...

Agree with backoff logic, Tested with fluentd log driver, looks like same there as well, except may be fluentd have some default lower backoff time (so that container stops more...

also 5mins time limit is from the default max-backoff we use. https://github.com/grafana/loki/blob/master/pkg/promtail/client/config.go#L19

The fix was already merged and released (should be available since > 2.0.1). Fix should be available in `grafana /loki-docker-driver`. checking if anything changed recently

@CptDaniel you are right. The fix is not included in any of the release yet. But if anyone using `grafana/loki-docker-driver:latest` (which is sync with latest master always) should contain the...