fix(opentelemetry): avoid storing inmemory if logs are disabled

[v1v]

SUMMARY

Workaround for #8353

Let's skip storing large datasets if the logs are disabled. This should help with the existing memory issues, so users can disable the logs. While we can figure out how to fix the underlying issue with storing large datasets.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

plugins/callback/opentelemetry

ADDITIONAL INFORMATION

[ansibullbot]

@v1v this PR contains the following merge commits:

• e602450

Please rebase your branch to remove these commits.

click here for bot help

[felixfontein]

Looks good to me! If nobody objects, I'll merge this this weekend.

[patchback]

Backport to stable-7: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply d87b9fe on top of patchback/backports/stable-7/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373

Backporting merged PR #8373 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-7/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373 upstream/stable-7

4. Now, cherry-pick PR fix(opentelemetry): avoid storing inmemory if logs are disabled #8373 contents into that branch:

   $ git cherry-pick -x d87b9fe0dce577aad2e58f56626a5df50839a884

   If it'll yell at you with something like fatal: Commit d87b9fe0dce577aad2e58f56626a5df50839a884 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x d87b9fe0dce577aad2e58f56626a5df50839a884

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR fix(opentelemetry): avoid storing inmemory if logs are disabled #8373 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-7/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@v1v thanks for your contribution!

[patchback]

Backport to stable-8: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply d87b9fe on top of patchback/backports/stable-8/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373

Backporting merged PR #8373 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-8/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373 upstream/stable-8

4. Now, cherry-pick PR fix(opentelemetry): avoid storing inmemory if logs are disabled #8373 contents into that branch:

   $ git cherry-pick -x d87b9fe0dce577aad2e58f56626a5df50839a884

   If it'll yell at you with something like fatal: Commit d87b9fe0dce577aad2e58f56626a5df50839a884 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x d87b9fe0dce577aad2e58f56626a5df50839a884

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR fix(opentelemetry): avoid storing inmemory if logs are disabled #8373 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-8/d87b9fe0dce577aad2e58f56626a5df50839a884/pr-8373

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

Manually backported in #8390 and #8391.