cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Kubernetes injection was not configured for this process

henk_stobbe
DynaMight Champion
DynaMight Champion

Hello,

Anybody know what Dt means by below message?

It is a ngnix process.

henk_stobbe_0-1718132760015.png

 

4 REPLIES 4

DanielS
DynaMight Guru
DynaMight Guru

Hello @henk_stobbe Could you please check if you have something of the type DO NOT MONITOR configured here:

DanielS_0-1718138307578.png

regarding NGINX pods?

The true delight is in the finding out rather than in the knowing.

henk_stobbe
DynaMight Champion
DynaMight Champion

Hallo Daniel,

Thanks for your reply, to be honest I did not check. But I am lucky (-;

henk_stobbe_0-1718139057863.png

 

Again thank you!

Hi @henk_stobbe 

I confirm you that Container Monitoring Rules disable processes injection as Daniel says. We've configured some rules here and it's disabled the deep monitoring in the processes running in the namespaces that match with the rules.

 

But in our case, Kubernetes is on cloudNativeFullStack and it shouldn´t apply the rules:

erh_inetum_2-1718167694679.png

But it's doing it!

We changed the deployment mode from classicfullstack to cloudnativefullstack.

Maybe this is reason for which the rules continue applying. Does anyone know if this may be the reason?

Regards,

Elena.

Daniel Elena,

Both, thank you for your great tips, but there was one (and wrong) namespace defined in the dynakube.yaml.

My apologies,but still great hints, thanks!

KR Henk 

Featured Posts