-
Notifications
You must be signed in to change notification settings - Fork 419
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
perform and service metrics not generated for windows agent when having Linux and windows integration in agent policy #726
Comments
Pinging @elastic/integrations (Team:Integrations) |
@manishgupta-qasource please review |
Reviewed & assigned to @EricDavisX |
@EricDavisX , When we reported defects, at that time, metricbeat error was logged in AGgnts logs. Later after more than an hour of time span, metricbeat service resumes it state to running on continuous hitting in backend[as per logs] and agent comes back to healthy state. Thus further, generating Windows.perform and service metrics data events on data set page. Issue reported: elastic/beats#24105 for metricbeat error We have same observations yesterday with Mac agent that metricbeat comes to running state after almost an hour and shared it under elastic/beats#23996 .MAC OS used was Apple Mac OS X 10.12 (64-bit) We have observed that this behavior is ON and OFF. Sharing a screenshot below: Screenshot: Window Agent Logs from Endpoint to trace exact timelines: Integration details: |
@dikshachauhan-qasource can you confirm explicitly the intent of the bug... I believe you are reporting that the functionality works when NOT combined together and only fails when the 2 Integrations are in use in the same Agent policy. Just confirming if this is the case, thank you |
Hi @EricDavisX It is working fine when we are using just windows or [System+Windows] package in Agent policy. This issue is only occurring when Linux combinations are used in Agent policy like:
Thanks |
|
Hi @EricDavisX cc @fearful-symmetry We have revalidated this issue on 7.11.1 snapshot Kibana cloud build having Linux package version 3.8 and found issue as Fixed.
Build details:
Hence, closing this issue. Thanks |
Build: 7.11.1 snapshot staging build
OS: windows 10 pro
Integration details:
"Linux" integration Version 0.3.7
"windows" Version 0.3.1
On installing agent using a policy having on windows and Linux integration only on Windows x64 bit, we observed that:
Screenshot:
![image](https://user-images.githubusercontent.com/72375798/108356581-52db1780-7212-11eb-8221-0930335528e7.png)
Build details:
The text was updated successfully, but these errors were encountered: