We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-English characters in EKS log got UNICODE-escaped in Cloudwatch logs.
abc, today is a good day 好雨知时节
This issue may related to fluent/fluent-bit#8521, which can resolved via building fluent-bit on graviton with flag -DCMAKE_C_FLAGS="-fsigned-char"
-DCMAKE_C_FLAGS="-fsigned-char"
part of EKS daemon set yaml
--- apiVersion: apps/v1 kind: DaemonSet metadata: name: fluent-bit namespace: amazon-cloudwatch labels: k8s-app: fluent-bit version: v1 kubernetes.io/cluster-service: "true" spec: selector: matchLabels: k8s-app: fluent-bit template: metadata: labels: k8s-app: fluent-bit version: v1 kubernetes.io/cluster-service: "true" spec: containers: - name: fluent-bit image: public.ecr.aws/aws-observability/aws-for-fluent-bit:stable imagePullPolicy: Always ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the question/issue
Non-English characters in EKS log got UNICODE-escaped in Cloudwatch logs.
This issue may related to fluent/fluent-bit#8521, which can resolved via building fluent-bit on graviton with flag
-DCMAKE_C_FLAGS="-fsigned-char"
Configuration
part of EKS daemon set yaml
Fluent Bit Log Output
Fluent Bit Version Info
Cluster Details
Application Details
Steps to reproduce issue
Related Issues
The text was updated successfully, but these errors were encountered: