-
Hi there,
We're ran into a case where the LogDNA Daemonset has issues connecting to `api.logdna.com`. In this case the pod will continue to run as normal. The only way we know if something it wron…
-
Migrating from LogDNA-agent to the Lambda integration, our JSON logs are not properly formatted in the LogDNA web app. The JSON body gets converted to a string, and log lines displayed in the web app…
-
Building and pushing s390x supported image to global registry icr.io/ext/logdna-agent.
-
I have a requirement where I need to create views per Kubernetes namespace in IBM Log Analysis tool. But I am not able to find a way to send the Namespace field as TAG using logDNA agent.
As most o…
-
The ask:
* A way to exclude /var/log and all other log directories implicitly included by default, and only ingest explicitly included files
* A way to ingest logs that are either in other directo…
-
I'm seeing a lot of duplicated lines since upgrading to v3.8.0. As an example, this line was reported multiple times over about a week of time:
![Screenshot 2023-04-04 at 11 44 32](https://user-ima…
-
Since logdna-agent is deprecated soon, we want to use v2 instead. But v2 does not support s390, do we have a plan to support it?
-
Trying to use extraEnv to change LOGDNA_LOG_DIRS.
Use the set above but end up with:
```
Error: INSTALLATION FAILED: YAML parse error on agent/templates/daemon_set.yaml: error converting YAML t…
-
this is a desc 123
Data Center:dallas
Region: dal12
Environment: preprod
Commands: kubectl get pods -A
-
fsgfsg salsa
Data Center:dallas
Region: dal13
Environment: preprod
Commands: kubectl get pods -A