Troubleshooting

​

View Collector Configurations

To view the current configurations of the collectors, you can check the ConfigMap objects in the odigos-system namespace.

You should see the processors configured under data/conf/processors, and actions configured under data/conf/pipelines.

Node Collector:

kubectl get cm -n odigos-system -o yaml odigos-data-collection

Gateway Collector:

kubectl get cm -n odigos-system -o yaml odigos-gateway

​

View Autoscaler Logs

The odigos-autoscaler controller is the component that watches for changes in the action or processor CRD and generates the collector configuration.

If you don’t see your processor in the collector configuration, you can check the logs of the autoscaler for errors or clues:

kubectl logs -n odigos-system deployments.apps/odigos-autoscaler

​

View Collector Logs

If you do see your processor in the collector configuration, and there’s an issue, the collector should log an error and will not start. To check the status of the Odigos pods, run:

kubectl get pods -n odigos-system

Look for pods with STATUS CrashLoopBackOff or Error.
To see the error, you can examine the logs of that pod:

kubectl logs -n odigos-system <pod-name>

You might find an error message like this:

* error decoding 'processors': unknown type: "invalid" for id: "invalid/example-processor" (valid values: [datadog experimental_metricsgeneration metricstransform resource servicegraph spanmetrics sumologic batch tail_sampling cumulativetodelta resourcedetection remotetap memory_limiter filter redaction routing span attributes deltatorate groupbyattrs groupbytrace k8sattributes probabilistic_sampler odigosresourcename])

If this is the case, then please follow the instructions in the error message to correct the processor configuration.

​

Getting Help

If you have any issues, or require our assistance, please open an issue in GitHub, or reach out to us in Odigos Slack