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 first option is to make a judgment call and enumerate the most popular APIs and add some high-value fields to those calls. For example, S3 API calls could include bucket names (and object keys), DynamoDB could include table names.
The second option is including the input (and maybe output?) as a single JSON-encoded field and users enabling automatic unpacking of nested JSON values (as per Honeycomb docs). Maybe this one should be an opt-in / opt-out.
Anyone have any thoughts?
The text was updated successfully, but these errors were encountered:
There are a couple of options:
The first option is to make a judgment call and enumerate the most popular APIs and add some high-value fields to those calls. For example, S3 API calls could include bucket names (and object keys), DynamoDB could include table names.
The second option is including the input (and maybe output?) as a single JSON-encoded field and users enabling automatic unpacking of nested JSON values (as per Honeycomb docs). Maybe this one should be an opt-in / opt-out.
Anyone have any thoughts?
The text was updated successfully, but these errors were encountered: