Skip to content
New issue

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 character got UNICODE-escaped when getting logs from EKS to Cloudwatch logs #825

Open
ensean opened this issue May 22, 2024 · 0 comments

Comments

@ensean
Copy link

ensean commented May 22, 2024

Describe the question/issue

Non-English characters in EKS log got UNICODE-escaped in Cloudwatch logs.

  • Input logs
abc, today is a good day
好雨知时节
  • Cloudwatch logs view
    image

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

---
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
...

Fluent Bit Log Output

Fluent Bit Version Info

Cluster Details

Application Details

Steps to reproduce issue

Related Issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant