-
Notifications
You must be signed in to change notification settings - Fork 204
Improve TestKubernetesJournaldInput #11256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve TestKubernetesJournaldInput #11256
Conversation
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors
|
This pull request does not have a backport label. Could you fix it @belimawr? 🙏
|
⏳ Build in-progress, with failures
Failed CI Stepscc @belimawr |
|
The failing tests seem unrelated: #11253 |
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
We've seen this on 9.2 also, so I believe we should backport to at 9.2. @belimawr thoughts about other backports? |
|
@Mergifyio backport 9.1 9.2 |
✅ Backports have been created
|
Yeah, that makes sense. Any active branch with this tests. |
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264)
|
I'll check all active branches with this test and create the backports. |
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264)
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264) # Conflicts: # testing/integration/k8s/testdata/journald-otel.yml
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264) # Conflicts: # testing/integration/k8s/testdata/journald-otel.yml Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors (cherry picked from commit 3062264) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors
- Log as ndjson so logs can easily be parsed/ingested into Elasticsearch - Set the log level to debug so we can see the events - If the test fails, log the index and search condition used - Improve `FindESDocs` to not log expected failures/errors
What does this PR do?
FindESDocsto not log expected failures/errorsWhy is it important?
It makes TestKubernetesJournaldInput easier to debug and likely fixes #11220
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry in./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E test## Disruptive User ImpactHow to test this PR locally
Related issues
TestKubernetesJournaldInputOtel–Condition never satisfied#11220Questions to ask yourself