Hi @GuilhermeAlbano,
Welcome to Google Cloud Community!
Here’s how to troubleshoot and fix it:
- Inspect the Log Causing the Issue:
To troubleshoot the issue, locate the full log message that triggered the error—this is typically found in the fluentbit-gke container logs.
Once identified, examine the specific log line causing the issue for further insights.
[error] [filter:gke] failed to parse operation: expected map, got string
kubectl logs <pod> --container=<container> | grep 'operation'
- Fix the Log Format:
If your application is emitting malformed operation fields, either remove the operation field entirely if it's not needed, or ensure it's properly structured with the correct fields.
- Sanitize Logs Before Emission:
If your application uses a logging library (such as in Go or Python), configure it to filter or format logs to match GCP’s structured logging requirements for compatibility.
- Verify Network Connectivity and Check Authentication/Authorization:
To ensure proper authentication and authorization, verify that Fluent Bit pods can access the Kubernetes API server by testing connectivity with kubectl commands, and confirm that the pods have the correct credentials and permissions if role-based access control (RBAC) is in place.
For detailed setup and troubleshooting tips, refer to the FluentBit documentation on Kubernetes integration. Additionally, consider contacting Google Cloud Support for help reviewing your project configuration and addressing any persistent issues.
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.
LinkedIn
Twitter
