Missing host information

[KIKON]

Hi, I can see, the namespaces, workloads and pods running, but when I try see node information or serice information I can not see nothing, in the host section appear this message:

Why?

[Fin_Ubels]

Hey Kikon,

How are you getting the K8s info? With the Dynatrace operator or by simply configuring the K8s integration? And if with the operator, what mode are you using?

[KIKON]

We use operator, but  I don't know the mode, I am not the administrator, I suppose the classic mode.

[KIKON · Accepted solution]

Hello, when I applyed the filter of Mzone, I didn't see the host metrics, when the filter was removed, I could see the information, but... the host was in the same Mzone that the workload, why? Well when I click in the name of some host and after I browsed for its properties I found a kubernetes node propertie, entity of type: KUBERNETE_NODE, for view the info this entities should be in the mzone. When I filter for Mzone this entity show permission problems. Fo this reason I view the message of mission host information.

[erh_inetum]

Hi Fin,

We have the same issue. 

We are getting K8 (Openshift) info with Dynatrace Operator in CloudNativeFullStack mode.

Thanks in advance.

Regards,

Elena.

[agrawal_shashan]

@KIKON Were you able to resolve this issue? I am also facing the same issue and we have also restarted our Pods to make sure One agent code modules gets injected but still seeing the same thing.

Any ideas?

[KIKON · Accepted solution]

Hello, I read in the community that this message is normal if you use some type of deployments, for example app only, in this case is normal you don't see host information, but if you use deployments of type classic full-stack, for example, this message is not normal and the reason may be: "But in your case is not normal, I guess that an error could be seen using describe in the pod from the kubectl CLI." I read this in this post: https://community.dynatrace.com/t5/Container-platforms/Re-quot-Missing-host-information-quot-message...

For me the option more probably is that in the host where some pods of specifics workloads are deployed, the oa is not deploy or no reporting for example license problems.

Thanks.!

[PacoPorro]

Check if the Activegate connected with the K8s/OCP cluster has enough resources.

[Peter_Youssef]

Hello @KIKON 

Kindly refer to the recommended approach by Dynatrace regarding K8s monitoring and compare against current deployment, it should resolve the exposed concerns.

https://docs.dynatrace.com/docs/setup-and-configuration/setup-on-k8s/installation/cloud-native-fulls...

If you will keep facing issues and troubleshooting each step, decommission and clean the old deployment files and start a fresh installation either following the guided UI or through the attached documentation URL.

BR,

Peter