removing info log#30971
Conversation
|
💚 CLA has been signed |
|
This pull request does not have a backport label. Could you fix it @solrac97gr? 🙏
NOTE: |
|
I already sign the Licence |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
/test |
@solrac97gr I checked I see the license signed with the hotmail address in your github profile, but the email for the commit is a gmail address. The CLA is looking at the commit email, not the PR. Either signing the CLA with your the gmail address in the commit or changing the commit to use your hotmail address will fix the check. |
kvch
left a comment
There was a problem hiding this comment.
Please do not remove this log message. It has helped me on many occasions to track down issues. Instead decrease the log level to debug.
|
@cmacknz changing no problem |
…eats into I30394-removing-console-log
* build and packages beats for darwin/arm64. The tar.gz package is called darwin-aarch64 * Osquerybeat: Add darwin/arm64 packaging support (#30935) Co-authored-by: Aleksandr Maus <aleksandr.maus@elastic.co> removing info log removing info log
…eats into I30394-removing-console-log
This reverts commit aa7065a.
…eats into I30394-removing-console-log
…eats into I30394-removing-console-log
|
already try changing mail and signin with both mails but not result |
I had to re-trigger the verification. It is signed now, and the CI checks can continue. |
|
/test |
|
/test |
…er-tar-gz * upstream/main: (139 commits) [Automation] Update elastic stack version to 8.3.0-c655cda8 for testing (elastic#31322) Define a queue metrics reporter interface (elastic#31289) [Oracle Module] Change tablespace metricset collection period (elastic#31259) libbeat/reader/syslog: relax timestamp parsing to allow leading zero (elastic#31254) [Automation] Update elastic stack version to 8.3.0-55ba6f37 for testing (elastic#31311) [libbeat] Remove unused fields and functions in the memory queue (elastic#31302) [libbeat] Cleaning up some unneeded helper types (elastic#31290) Readme for kibana module (elastic#31276) [Automation] Update elastic stack version to 8.3.0-4be61f32 for testing (elastic#31296) x-pack/winlogbeat/module/routing/ingest: fix typo for channel name (elastic#31291) Small pipeline cleanup removing some unused data fields (elastic#31288) removing info log (elastic#30971) Simplify TLS config deserialization (elastic#31168) Detect new files under known paths in filestream input (elastic#31268) Add support for port mapping in docker hints (elastic#31243) Update qa-labels.yml (elastic#31260) libbeat: log debug for `proxy_url` and fixed docs (elastic#31130) [heartbeat][docs] Add note about ensuring correct index settings for uptime (elastic#31146) [Automation] Update elastic stack version to 8.3.0-2c8f9574 for testing (elastic#31256) [Filebeat] fix m365_defender pipeline bug (elastic#31227) ...
Log start of filestream scan at debug level Co-authored-by: carlos97gr <carlosgperu97@gmail.com> Co-authored-by: Craig MacKenzie <craig.mackenzie@elastic.co>
|
Is it possible backport this change to 7.17? We will stay at 7.17 for a long time. |
Log start of filestream scan at debug level Co-authored-by: carlos97gr <carlosgperu97@gmail.com> Co-authored-by: Craig MacKenzie <craig.mackenzie@elastic.co> (cherry picked from commit 5478d73)
Log start of filestream scan at debug level Co-authored-by: carlos97gr <carlosgperu97@gmail.com> Co-authored-by: Craig MacKenzie <craig.mackenzie@elastic.co> (cherry picked from commit 5478d73) Co-authored-by: Carlos García Rosales <carlosgarcia_97gr@hotmail.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Log start of filestream scan at debug level Co-authored-by: carlos97gr <carlosgperu97@gmail.com> Co-authored-by: Craig MacKenzie <craig.mackenzie@elastic.co>
What does this PR do?
Remove the info log, because this were generating unnecessary logs.
Why is it important?
That generate a big number of log who can distract of the real problem.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
check in the watch logs there is not showing the "Start Next Scan" log
Related issues
Use cases
Scenario: Your Watch get a Event
When the Watcher have new Event
Then the Watcher will not create a log with "Start Next Scan" in every event
Screenshots
Logs