Storage.interestGroupAuctionNetworkRequestCreated Event returns array of IG auction IDs than informing the exact IG auction-id

[pm-harshad-mane]

We are using Storage.interestGroupAuctionNetworkRequestCreated event to listen to gather information of KV calls.
Following is link for the documentation,
https://chromedevtools.github.io/devtools-protocol/tot/Storage/#event-interestGroupAuctionNetworkRequestCreated
Specifies which auctions a particular network fetch may be related to, and in what role. Note that it is not ordered with respect to Network.requestWillBeSent (but will happen before loadingFinished loadingFailed).

For each auction a separate KV call is triggered and a unique Network requestId is created but this event is returning an array of IG
auction-ids on the page than informing the exact IG auction id for which this KV call with given network request ID is made.

We need this for debuging, #937

[morlovich]

So to be precise, this is the list of auctions using the worklet at the moment of the fetch. The signals can come from any combination of them (and we don't actually keep track of from which). Related, the worklet will fetch JS (and wasm) only once, so other auctions sharing them will reuse that fetch.

[pm-harshad-mane]

Hi @morlovich ,
Worklets are typically static files, and they often serve as shared resources across multiple PAA instances. Therefore, it seems logical to return an array of auction IDs for Worklets.
However, KeyValue server calls are dynamic and can vary for each auction.
Hence, I suggest that the API distinguishes between Worklet and KeyValue calls and returns the specific auction ID for KeyValue calls instead of providing an array of auction IDs

[MattMenke2]

There isn't a specific auction ID - requests from multiple auctions can be merged, if the parameters are all the same.