Skip to content

RequestIds in PostExecutionStart/Stop events are not unique for different call stacks #1302

@jialongcheng

Description

@jialongcheng

Bug description

PostExecutionStartEvent and PostExecutionStopEvent both contain a request ID. Users should be able to uniquely identify the events based on the request Id and correlate the start/stop event pairs for processing.

In our performance testing, we found out that sometimes different tasks had same request ID. Here is a snapshot of the events:
image

These events have the same id but from the call stacks of the Start events, they are clearly not from the same task.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions