Issue

Pod or syslogs are not visible in the OpsRamp portal, even though the Kubernetes 2.0 agent pods are running.

Cause

1. Logs not Enabled
   • During Kubernetes 2.0 integration, the logs option was not enabled.
   • The manifest file may not have logs.enabled set to true.
2. Portal Setting not Enabled
   • In the OpsRamp portal, Log Management must be enabled at the client level. If disabled, logs will not appear.
3. OpenTelemetry Pipeline not Running
   • The Kubernetes 2.0 agent uses the OpenTelemetry pipeline to collect logs. If the pipeline fails to start, logs will not be collected.
4. Namespace Configuration
   • Logs may not appear for certain namespaces if they are disabled in the ConfigMap.

Solution

1. Enable Logs in Manifest
   • Edit the manifest and set logs.enabled to true.
   • Update the endpoint with your OpsRamp portal URL:

     logs:
       enabled: true
       endPoint: "https://<opsramp-portal>.api.opsramp.net"

2. Enable Log Management in Portal
   • Go to Client Details Page > Log Management.
   • Ensure Enable Log Management is set to Yes.
3. Verify Pipeline Status
   • Confirm whether the logs pipeline has started.
   • Check agent logs to validate that the OpenTelemetry pipeline is running.
4. Review Namespace Configurations
   • If logs are missing from specific namespaces, edit the ConfigMap to include or exclude namespaces as required:

     kubectl edit configmap <k8s-log-configmap> -n <namespace>

   • Adjust the configuration as needed for infrastructure metric collection.
5. Cross-check in Portal
   • Navigate to the Logs section in the OpsRamp portal.
   • Verify pod logs and, if configured, syslogs are visible.