-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add a new E2E test to confirm that Elastic Agent component logs can be shipped to Fleet #2402
Comments
This test should also change the agent log level to debug and confirm that each process generates at least one debug log. We'll have to look at some representative logs to find a few that are always generated. |
Marking this one as P0 as we're keep breaking our debug logs |
@pierrehilbert what's blocking us here? |
Nothing anymore, just updated the status. |
Currently blocked by a handful of bugs and rough edges in the testing framwork. The biggest actual blocker is here: elastic/elastic-agent-libs#127 |
What do we want to do and why?
Implement an E2E test that enrolls an agent in Fleet and ensures that logs are shipped to the expected set of logs datastreams. This tests automates enrolling an agent in Fleet and manually inspect the logs messages in the UI box below.
logs-elastic_agent-default
,logs-elastic_agent.filebeat-default
andlogs-elastic_agent.metricsbeat-default
datastreams:"Parsed configuration and determined agent is managed by Fleet"
can be queried fromlogs-elastic_agent-default
.metricbeat start running.
can be queried fromlogs-elastic_agent.filebeat-default
filebeat start running.
can be queried fromlogs-elastic_agent.metricsbeat-default
.The steps in this test touch a large surface area of the agent and Fleet product and would have automatically detected several recent regressions, notably:
Definition of done
The text was updated successfully, but these errors were encountered: