Use unique index for TestOtelLogsIngestion

[belimawr]

What does this PR do?

Use unique index for TestOtelLogsIngestion

Why is it important?

TestOtelLogsIngestion was flaky and could cause other tests to become flaky due to mapping conflicts, using a unique index fixes the problem.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• 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
• I have added an integration test or an E2E test

## Disruptive User Impact

How to test this PR locally

Start a Elastic Stack and export the following env vars:

ELASTICSEARCH_HOST
ELASTICSEARCH_USERNAME
ELASTICSEARCH_PASSWORD
KIBANA_HOST
KIBANA_USERNAME
KIBANA_PASSWORD

Package and run the tests:

# Package Elastic Agent, adjust according to your OS
DEV=true SNAPSHOT=true EXTERNAL=true PACKAGES="tar.gz" PLATFORMS=linux/amd64 mage -v package

# Run the tests, adjust according to your OS
DEV=true SNAPSHOT=true EXTERNAL=true PACKAGES="tar.gz" PLATFORMS=linux/amd64 AGENT_VERSION="9.3.0-SNAPSHOT" mage -v integration:local TestOtelLogsIngestion

Related issues

• Closes [Flaky Test]: TestOtelLogsIngestion – Expected 10000 logs, got &{0} #7222

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @belimawr? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[belimawr]

The failing test is not related to this PR, there is already an issue for it: #5437

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-TestOtelLogsIngestion upstream/fix-TestOtelLogsIngestion
git merge upstream/main
git push upstream fix-TestOtelLogsIngestion

[belimawr]

The last failure was an issue while creating the ESS deployment: https://buildkite.com/elastic/elastic-agent/builds/30818/steps/canvas?sid=019aa722-5811-487f-ae5e-c54d039de546#019aa726-853e-4a44-9f47-b9325815f8cd/150-329

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 4aefecd

Failed CI Steps

• Trigger Serverless Beats Tests

History

• 💔 Build #30818 failed 5e0ff71
• 💔 Build #30779 failed 70e1745
• 💔 Build #30699 failed a102f02
• 💔 Build #30543 failed d484ce6

cc @belimawr

[belimawr]

I created a issue for the BK failure: elastic/beats#47767

[github-actions]

@Mergifyio backport 8.19 9.1 9.2

[mergify]

backport 8.19 9.1 9.2

✅ Backports have been created

• #11419 [8.19] (backport #11254) Use unique index for TestOtelLogsIngestion has been created for branch 8.19
• #11420 [9.1] (backport #11254) Use unique index for TestOtelLogsIngestion has been created for branch 9.1 but encountered conflicts
• #11421 [9.2] (backport #11254) Use unique index for TestOtelLogsIngestion has been created for branch 9.2