Skip to content

Conversation

beniwohli
Copy link
Contributor

it turns out that setting the agent multiple times can
result in difficult-to-debug issues, especially when
initially using the DjangoClient, and having it replaced
with a "bare" Client. See #1093, #1148

By bumping this log message to WARNING, it is a bit more
obvious what the problem could be.

it turns out that setting the agent multiple times can result in difficult-to-debug issues, especially when initially using the DjangoClient, and having it replaced with a "bare" Client. See elastic#1093, elastic#1148 By bumping this log message to WARNING, it is a bit more obvious what the problem could be.
@ghost
Copy link

ghost commented Jun 14, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #1164 opened

  • Start Time: 2021-06-14T08:17:17.744+0000

  • Duration: 27 min 33 sec

  • Commit: ce0fcf3

Test stats 🧪

Test Results
Failed 0
Passed 9535
Skipped 8766
Total 18301

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 9535
Skipped 8766
Total 18301

@beniwohli beniwohli merged commit 8387a7d into elastic:master Jun 14, 2021
@beniwohli beniwohli deleted the multiple-agents-warning branch June 14, 2021 15:19
beniwohli added a commit to beniwohli/apm-agent-python that referenced this pull request Sep 14, 2021
it turns out that setting the agent multiple times can result in difficult-to-debug issues, especially when initially using the DjangoClient, and having it replaced with a "bare" Client. See elastic#1093, elastic#1148 By bumping this log message to WARNING, it is a bit more obvious what the problem could be.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants