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.

Sign up for GitHub

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

Jump to bottom

[System test runner] Allow access to Agent and underlying Beats logs when testing #86

Closed

ycombinator opened this issue Sep 8, 2020 · 1 comment

Labels

Contributor

ycombinator commented Sep 8, 2020

Follow up to #64, based on suggestion in #64 (comment):

The agent log file can go to tmp. We can monitor this one for potential errors. I wonder if we can do the same for metricbeat and filebeat logs.

... it's a rather a nice-to-have feature to also observe programmatically logs of elastic-agent, filebeat and metricbeat while testing. Many configuration errors are reported deep down by filebeat or metricbeat's internals.
Logs can be collected in the same single directory and exported as volume.

ycombinator mentioned this issue

System test runner MVP #64

Merged

mtojek mentioned this issue

Elastic-Agent Docker: silent standard output elastic/elastic-agent#302

Closed

ycombinator added the enhancement label

Contributor

mtojek commented Oct 6, 2021

It might be hard to do this automatically as there isn't still unified error logging format, but we're able to collect CI logs now.

mtojek closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment