Roger Coll
Roger Coll
The current lifecycle of the podman's receiver (also the docker one) depends on the `start` scraper's functionality. On start, it tries to get all the healthy containers so it does...
For the moment, I create PR to align the shutdown method with the dockestats receiver.
Hi @haihongren , Could you add some end-to-end tests in https://github.com/newrelic/nri-flex/tree/master/test/testbed that cover this use case? In addition, could you sign the commits? Thanks for the contribution!
Hi @Kav91 , Could you add some end-to-end tests cases in https://github.com/newrelic/nri-flex/tree/master/test/testbed that cover this use case? Thanks for the contribution!
@Kav91 Good point! I just created a task for the team to do so. Thanks for pointing that out.
If you agree that could be useful I can start working on it.
@akrantz01 @popey Could you take a look at https://github.com/influxdata/telegraf/pull/9634 ? Initial PR with some basic monitoring for Podman. Best regards
As the `slab` memory term is unique to the Linux kernel, I would follow the same approach as in https://github.com/open-telemetry/semantic-conventions/issues/257 and add the `system.linux.memory.slab` metric. Also, remove the `slab` state...
> @rogercoll Could you file a PR for this? I think that makes sense to me indeed Sure, I'll file a PR for this. Thanks!