You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The elastic beanstalk format that goes to cloudwatch is something like this:
Oct 26 16:50:00 ip-172-31-1-156 web: {{log}}
The expectation is that the {{log}} element is extracted, and it gets parsed and if it's a json, the elements of the json will be visible in logz.io, but this is not the case. The whole message appears as a string. The old method using cloudwatch and lambda functions worked correctly.
The text was updated successfully, but these errors were encountered:
The elastic beanstalk format that goes to cloudwatch is something like this:
Oct 26 16:50:00 ip-172-31-1-156 web: {{log}}
The expectation is that the {{log}} element is extracted, and it gets parsed and if it's a json, the elements of the json will be visible in logz.io, but this is not the case. The whole message appears as a string. The old method using cloudwatch and lambda functions worked correctly.
The text was updated successfully, but these errors were encountered: