Thanks, I did try that config earlier but from what i can see this is not compatible with the later istio builds - it uses logentry/metric/cloudwatch CRDs that are not present.
I eventually got it working via configuring handler/instance/rule resources based upon the prometheus adapter config included in the helm charts.
Were you ever able to update docs? I am new to istio and trying to figure out how to send istio logs to cloudwatch, and am completely stumped. I read up on the mixer adapter model and learned a bit about handlers, templates, and instances, but am confused if I need to write my own for the cloudwatch adapter, and if so what files I actually need to create, and what they should look like.
I tried looking for the prometheus adapter config but didn’t have any luck
@studees Did you ever get the cloudwatch template working with a logentry? I keep getting error adapters failed to get message for instance: accesslogentry.instance.istio-system. failed to evaluate template for log instance: &{accesslogentry.instance.istio-system map[destination_ip:�� destination_service:unknown latency:199.372µs method:GET protocol:https request_size:%!s(int64=0) response_code:%!s(int64=404) response_size:%!s(int64=0) source_ip:��
@studees Would you mind also supplying your handler? I am still running into failed to evaluate template for log instance errors. Thank you for your reply!
Thank you very much, I believe my issue was that I wasn’t addressing fields in the payload template with their name before their value. So for payload template I just had .sourceApp instead of sourceApp: .sourceApp
Hello there - Do you know if there is any better documentation around this topic? Im struggling to understand what adapter these resources refer to in cloud watch is it the container insights adapter, if not which agent do I need to install to scrape istio metics envoy logs into cloud watch?
Is this the bets way to get logs and metrics from istio into cloudwatch or would using Fluent D and prometheus cloudwatch adapter be a better path?
@fostpau at this point, using a fluentd + prom->cloudwatch solution would be a better path. the mixer adapters are deprecated (and completely removed in 1.8).