Skip to content

Support messages with non-ascii characters in splunk-cloudwatch-logs-processor #17

Description

@cazlo

What

When handling logs with non-ASCII information, the splunk-cloudwatch-logs-processor lambda blows up

Why

This is because it is trying to read the event string using the ASCII encoding
https://github.com/splunk/splunk-aws-serverless-apps/blob/master/splunk-cloudwatch-logs-processor/index.js#L46

Quick Fix

A quick fix for this is to instead use utf-8 encoding when reading the AWSevent

Reproducing this issue

  1. base64 decode the sample event
  2. add some Chinese characters to one of the messages
  3. base64 encode sample event
  4. run integration test
  5. observe test failure

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions