[DataUsage][Serverless] Log more info on autoops 503 errors

ashokaditya commented 2 weeks ago

Summary

Adds error info from auto ops when we see 503 errors while making a request to autoops service.

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
[ ] Documentation was added for features that require explanation or tutorials
[ ] Unit or functional tests were updated or added to match the most common scenarios
[ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
[ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
[ ] Flaky Test Runner was used on any tests changed
[ ] The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

elasticmachine commented 1 week ago

Buildkite Build
Commit: 0b3bd3417bb149b9437bfbb6f69caf1fdb55577f
Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-202350-0b3bd3417bb1

✅ unchanged

cc @ashokaditya

kibanamachine commented 1 week ago

Starting backport for target branches: 8.x

kibanamachine commented 1 week ago

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.