Add additional transaction labels with error details to requests.

[michel-laterman]

What is the problem this PR solves?

It's difficult to determine if a fleet-server error is caused by a downstream elasticsearch error, or it indicates an actual issue (fleet-server misconfiguration etc.)

How does this PR solve the problem?

Add transaction labels with more error details when a request would send an APM error.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

• Closes Enrich traces and request logs with Elasticsearch error details #3098

[michel-laterman]

@joshdover is this closer to what you had in mind (in the issue description)?

[joshdover]

Yes this makes sense to me. One thing I can't tell from just reading this is if any of these fields contain anything instance-specific content that will create noise and make it harder to group related errors, such as specific disk usage stats, node names, etc. This would probably be tricky to normalize though at this point and I think we can do this at query time later if it's an issue.

[michel-laterman]

ok, we'll merge as is for now and we can revist/clean up the labels in the future

[joshdover]

Yes this makes sense to me. One thing I can't tell from just reading this is if any of these fields contain anything instance-specific content that will create noise and make it harder to group related errors, such as specific disk usage stats, node names, etc. This would probably be tricky to normalize though at this point and I think we can do this at query time later if it's an issue.

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

100.0% Coverage
0.0% Duplication