Troubleshooting
Problem
The Instana Agent is installed in the Kubernetes cluster. It is listed in the Infrastructure view, but not in the Kubernetes view.
Cause
This issue occurs when the agent is installed by using the YAML method. However, reinstalling with the operator method did not resolve the issue as the incorrect key was used.
Log messages:
[root@ip-1-1-1-1 instana]# kubectl logs k8sensor-xxxx-nxx -n instana-agent
2023/01/01 01:01:11 maxprocs: Updating GOMAXPROCS=1: using minimum allowed GOMAXPROCS
2023/01/01 01:01:11 using in-cluster configuration
2023/01/01 01:01:11 app=k8sensor@axxc host=k8sensor-xxxx-nxxxx backend=https://abc-saas.instana.io:443 agent_key=replace-key zone=uat-xx-kxxxx-uid=123abc-12ws-1232-abc12-12312312abc name=instana-agent/k8sensor-xxx-nxxxx ip=1.1.1.1 cluster-uid= burst=0 qps=0 snitch
Environment
SaaS
Resolving The Problem
Make sure to use the correct agent key in the CRD file 'instana_v1_instanaagent.yaml' and reapply it. You might need to restart the k8sensor deployment afterward.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSE1JP5","label":"IBM Instana Observability"},"ARM Category":[{"code":"a8m3p000000UoUGAA0","label":"Agent"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
05 January 2024
UID
ibm17101010