Troubleshooting page

Common Issues

Issue 1. Pods Not Running

Symptoms:

• kubectl get pods shows CrashLoopBackOff or ImagePullBackOff.

Solutions:

1. Check logs:

kubectl logs -n middleware -l app=middleware-agent

2. Invalid API Key:
   • Verify your API key.
   • Re-deploy with helm upgrade.

Issue 2: No Data in the MiddleWare dashboard

Symptoms:

• No metrics/logs after 5+ minutes.

Solutions:

1. Check network policies:

kubectl describe pod -n middleware middleware-agent-abcde

2. Allow egress to ingest.middleware.io:443.

Method-Specific Fixes

Helm

• helm upgrade fails:

helm rollback middkubectlt <REYAML errorsleware

Issue 3: Applications not detected after auto-instrumentation

Solutions:

• Check if your application uses a supported programming language.
• For multi-container pods, ensure main application container is first in the pod spec.
• Ensure applications are running and healthy.
• Check language detector logs for potential issues.
• Restart the language detector if detection problems persist.

Issue 4: Instrumentation not working:

• Ensure the namespace is enabled for auto-instrumentation.
• Confirm the application was restarted after enabling instrumentation.
• Confirm required annotations are present in object YAML.
• Examine webhook admission errors and mw-autoinstrumentation namespace component logs.
• Verify network connectivity to Middleware endpoints.
• Check opentelemtery operator logs.