2

Log UUID in Events metadata generated by an API Batch Call

It's possible to execute a number of operations via a single call to the API batch method. This helps reduce the number of server roundtrips, but it can sometimes make it difficult to sort out all the Events that were generated from a single batch call.

This request is to add a UUID to the meta value of Events so users can easily identify from which batch a given Event was generated. Would this be useful to you? Add your vote and additional use cases below.

3 comments

  • 0
    Avatar
    Tony Aiello

    Ideally we'd want to generate and supply the Batch UUID ourselves via an optional *string* arg to the .batch() call.  In that way the EventLogEntries resulting from 2 or more "related" batch calls could be identically identified, and we could pack other useful metadata into the Batch ID string such as user and/or host-IP and/or a description, etc.

  • 0
    Avatar
    Tony Aiello

    Hi, also, it would be better if this value went into an actual separate new field on EventLogEntries instead of just into the ['meta'] json blob, because that blob is not filterable nor sortable nor queryable with the native Shotgun UI filter tools, and API queries would be extra-slow because it would have to do a plain-text 'contains' aka a SQL 'LIKE' call.

  • 0
    Avatar
    Tony Aiello

    Dunno if you want to mark this feature 'Solved' or 'Delivered' or 'Released' -- the API's existing .set_session_uuid() method coupled with querying the ['session_uuid'] field on EventLogEntries pretty much fully covers this feature request.  Thanks for the tip, Brandon!

Please sign in to leave a comment.