-
We need to improve logging throughout the whole framework and enable the user to configure verbosity as well as output of the logs.
- agent already has log level as property so we'll only need to p…
-
### Specification
The change made in #157 was not done fully according to our standards. We should use the existing logging system for this message. So the following changes need to be made.
1. …
-
Recently the `agent.logging.level` was exposed via the Agent Policy so that users can modify this setting globally per policy.
There are a few more agent logging settings which would also be beneficia…
-
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
- `python3 -sBm build -w --no-isolatio…
-
I think it's been a while since we spent some time poking through agent logs and making sure they're easy to understand, not overly polluted, and correctly formatted. In debugging I've noticed a few t…
-
-
Hi,
we are encountering the below issue.
After upgrading the module to v7.0.2. We restarted VMs and started getting errors to ship logs to statsd
```sh
vault[3436]: [ERR] Error flushing to stats…
-
Hi @JumpingYang001
I hope you are well. We seem to be experiencing this problem again and I would like to reopen this ticket to try and resolve this again please.
Kind regards
No…
-
With the release of Debian 12 (bookworm) a fresh install will default to using Wayland (instead of X11 / X.org) as its windowing environment.
Note that, as bookworm continues to support X11/X.org, …
-
## Cilium Feature Proposal
**Describe the feature you'd like**
Currently, the Cilium Agent writes its logs to stdout, and containerd eventually writes these logs to a folder under `/var/log/pods…