Using scheduling for Apigee trace instead of manual work with control

[fodornorbert199]

Currently we are using EdgeUI to start tracing for API testing and it's automatically turn off after 10 minutes so continuous monitoring needed during the tests. We want to automate this, and the goal is to use some scheduling or something like that, to start trace logging and stop after tests finished and save the logs to a specified place. Illustrated by an example: We know that one of our consumer wants to test our API named API-1 on 30th of November from 2 pm to 3 pm. We want to start trace without manpower at 2 pm and stop at 3 pm. After they finished their tests logs are should be saved to a specified folder.

Is it possible?

[#2]

As per my understanding, trace is a live debugging tool. There is way to download trace using management api call.

[fodornorbert199]

Maybe my question was not totally clear, so below you can see the trace tool, with a started trace session, which is limited to 10 minutes. We want to start trace sessions for APIs automatically (based on an agreement with our consumer) at a certain time for a given time range while the consumer doing tests and after the time frame expired trace session stopped and logs saved.

[fodornorbert199]

As I see the picture is missing from my previous comment so I attached again.

[ylesyuk]

Keep in mind that trace adds a processing overhead. So it should be used sparingly.

You can achieve not exactly this, but you can get pretty close by using this wrapper around management api so you can keep creating trace sessions using crontab or similar.

https://github.com/yuriylesyuk/ets

If you are on OPDK, you can use different approach to increase a number of requests, discussed here:

https://community.apigee.com/questions/39080/increasing-the-limit-of-trace-messages-in-edge-on.html

Here are examples of complicated situations when the tool was successfully used:

https://community.apigee.com/questions/71053/finding-one-error-among-thousands-of-successes.html

https://community.apigee.com/questions/79062/identify-source-of-30-second-proxy-latency.html