​
Validating Helm Release

Before moving forward, it’s essential to verify the installation. We need to ensure that the pods for the collector-manager are in a healthy state and running without experiencing crash loop backoff. Finally, we also need to ensure that the values set in TENANT_ID and INTEGRATION_ID match the corresponding values in Overview Page.
  • Before proceeding, it’s crucial to confirm the Helm installation’s integrity. To verify the installation, execute the following command:
    copy
    helm status plerion-collector-manager -n plerion-system
    Example output: 
    NAME: plerion-collector-manager
LAST DEPLOYED: Tue Nov 21 09:18:00 2023
NAMESPACE: plerion-system
STATUS: deployed
REVISION: 1
  • To verify the operational status of collector-manager pods, execute the following command:
    copy
    kubectl get pods -n plerion-system
    Example output: 
    NAME                                                 READY   STATUS    RESTARTS   AGE
plerion-collector-manager-ccbc55c5d-dr27w   1/1     Running   0          10m
plerion-collector-manager-ccbc55c5d-x255n   1/1     Running   0          10m

    ​
    Common Issues and Troubleshooting

    • Pods in CrashLoopBackOff State: If you encounter pods repeatedly entering the CrashLoopBackOff state, inspect the pod logs for error messages. This could indicate issues with application configuration or dependencies.
    • Pending Pods: Pods in a “Pending” state may indicate resource constraints or configuration problems. Check resource requests/limits and ensure the necessary configurations are in place.
  • To view the currently applied secret in your collector-manager, execute the following command:
    Warning: Be cautious when running this command, as it may potentially reveal the secret in plain text.
    copy
    kubectl get secret plerion-collector-manager -n plerion-system \
    -o go-template='{{range $key, $value := .data}}{{printf "%s: %s\n" $key ($value| base64decode )}}{{end}}'
    Example output: 
    INTEGRATION_ID: [redacted]
INTEGRATION_KEY: [redacted]
TENANT_ID: [redacted]
  • To view the currently applied configmap in your collector-manager, execute the following command:
    copy
    kubectl get configmap plerion-collector-manager -n plerion-system \
    -o go-template='{{range $key, $value := .data}}{{printf "%s: %s\n" $key $value }}{{end}}'
    Example output: 
    APP_URL: https://au.app.plerion.com
CLIENT_BURST: 10
CLIENT_QPS: 5
HEALTH_PROBE_BIND_ADDRESS: :8081
HTTP_MAX_RETRY_ATTEMPTS: 3
HTTP_MAX_RETRY_BACKOFF: 30s
HTTP_MIN_RETRY_BACKOFF: 1s
LEADER_ELECTION: true
METRICS_BIND_ADDRESS: :8080