Dmitri Khokhlov

@clnperez contributions are welcome. specifically - to resolve build problems on these ^^^ targets.

hi @maxfliri could you collect "bad case" logs from agent running with this env var RUST_LOG=debug? full log.

fix PR: https://github.com/logdna/logdna-agent-v2/pull/496 there is also another fix in development now for the same issue. cc: @jakedipity

etc/logdna.env is specified in logdna-agent systemd service config. does your linux uses systemd?

We've reproduced the log flood issue. Working on the fix.

The doc does say that agent is using systemd. https://github.com/logdna/logdna-agent-v2/blob/master/docs/LINUX.md#usage. And all steps are done in that context.

do you mean - be able to search in Web UI by value from this NAMESPACE env var? https://github.com/logdna/logdna-agent-v2/blob/master/k8s/agent-resources.yaml#L155

how about to define new env var in yaml: ``` - name: LOGDNA_TAGS valueFrom: fieldRef: fieldPath: metadata.namespace ``` similar to the link i mentioned.

403 Forbidden - is about Ingestion Key. LOGDNA_TAGS - is static field. Cannot be modified on the fly with each line. Agent does have k8s enrichment of log lines. Do...

> UPDATE: > > The agent configuration works fine with just the two below-mentioned mounts as well. Should I still consider using other volumes as well? > > ```yaml >...