Move Job from RequestTelemetry to DependencyTelemetry

[knopa]

trafficstars

Move Job from RequestTelemetry to DependencyTelemetry Add Bypass Activity id, RootId to chain operations in AI

[knopa]

Hey @coolhome I have improved a little your project, can you check that PR?

[coolhome]

I see using Dependency makes it easier to see how jobs got started from a web request. However, for recurring jobs they become tucked away under dependency. I originally used Operation to see my recurring jobs as operations.

I'm going to look into making recurring jobs an operation, and enqueue as a Dependency.

[knopa]

Now it can be switch between request or dependency depends on your need

[coolhome]

@knopa I've been playing around with this and I was wondering if this solves your problem and more? This is what I was originally aiming for when I built this but never took the time to implement.

[knopa]

Yes. Because if you need to separate Request from Dependecies it could be an issue with original implementation. On one project it affect the requests stats especially the response time. Also there wasn't a way to chain the full flow of user interaction with your request to jobs etc. Now you able to choose which fit better to your project as example for one project i set it as dependencies telemetry on another as requests telemetry.

[knopa]

Now if you got request enque job and it failes - you can trace back to origin request.

[zbend]

Can we merge this?