fix: fix e2e unstable

[LiuTianyou]

What's changed?

1. fix e2e unstable

Checklist

• I have read the Contributing Guide
• I have written the necessary doc or comment.
• I have added the necessary unit tests and all cases have passed.

Add or update API

• I have added the necessary e2e tests and all cases have passed.

[LinuxSuRen]

api-testing has the similar way to check if the server is ready. But it cannot send a payload to the endpoint.

I'm wondering if there is an API for the health check. Return status code 200 when the server is ready to accept requests.

[LiuTianyou]

api-testing has the similar way to check if the server is ready. But it cannot send a payload to the endpoint.

I'm wondering if there is an API for the health check. Return status code when the server is ready to accept requests.200

@LinuxSuRen Hello, thanks for your reply. I used the login API of hertzbeat to check whether the service is ready, but it seems that the e2e instability is not caused by inaccurate health checks.We have encountered a situation where the API that requires authentication occasionally fails in the test case. Is there a debug mode in api-testing that can output more log information, such as the URL, header, payload of the sent http request, etc. to help us troubleshoot this problem?

[LinuxSuRen]

Sure. You can add the log output level flag, such as: atest run --level debug

[LiuTianyou]

Sure. You can add the log output level flag, such as: atest run --level debug

@LinuxSuRen Thank you. got it

[yuluo-yx]

Sure. You can add the log output level flag, such as: atest run --level debug

@LinuxSuRen Thank you. got it

Current log message warn level

[yuluo-yx]

LGTM

[yuluo-yx]

@Aias00 if no other problem, maybe we can merge it, Let's see if the e2e test after that works.

[Aias00]

@Aias00 if no other problem, maybe we can merge it, Let's see if the e2e test after that works.

sure