Kapil Thangavelu
Kapil Thangavelu
regarding seeing api calls, the easiest is probably via the builtin aws sdk instrumentation capabilities, ie. https://boto3.amazonaws.com/v1/documentation/api/1.14.0/guide/sdk-metrics.html an alternative, you can optionally enable X-ray tracing via the cli (--trace xray)...
i typically use https://vector.dev with csm as a sink/log of calls here's the config file i use for vector, and then i just set the AWS_CSM* env vars up. ```toml...
hmm.. I don't recall needing this in log exporter for cross account kinesis delivery (its original use case), but sure happy to have support in their for role arn specification...
merged in #7617
eks and s3 make sense for sure, the container from ebs feels a bit trickier (ie. reporting it against the ebs volume doesn't nesc correlate it back to the "compute")....
I'm a little unclear what you mean when you say json can't be loaded programmatically... what are you using to process json lines format?
I found this overview of the different format names for essentially the same thing somewhat helpful https://github.com/ndjson/ndjson.github.io/issues/1#issuecomment-109935996
I think this is useful, but I do have concerns about a bunch of resources getting flagged with the default behavior here, re service account access to resources without conditions...
ping @cloud-custodian/azure
ping @cloud-custodian/azure