Remove prefix in the usage insights operation name

[noghartt]

Hey guys, the "Insights" tab brings some really good insights around our GraphQL operations. One specific edge case I've found, is about the hash in the prefix of the operations.

I'd like to know if there is any specific way to customize or remove this prefix, since it can increase a bit of the cardinality in the usage report for same operations (ideally, we'd like to see it in a macro-view).

Seeing the Usage Report Schema, if I right understood, the prefix is based on the map key + operationMapKey.

So I'd like to know if there's any specific way to manage/customize this part?

[n1ru4l]

Hey @noghartt, The hash prefix is added so Insights can aggregate data per unique GraphQL operation, not just per operation name. It’s based on the operation’s actual shape, which prevents different queries with the same name from being grouped together. This keeps performance and error data accurate, even if it increases cardinality in usage reports.

We currently do not have any plans for altering this behaviour or providing ways to customize it.

[noghartt]

Gotcha, thanks for the reply @n1ru4l! In case, do you recommend any specific way to manage a kind of custom report to track the average statistics including any hash prefix operation?