Skip to content
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

Update windows integration package spec to v3 #10781

Merged

Conversation

belimawr
Copy link
Contributor

Proposed commit message

This commit updates the windows integration to package spec v3.2.1 and makes all necessary changes to the dashboards and fields definitons.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

## Author's Checklist

How to test this PR locally

  1. Build the windows package
  2. Start a stack using elastic-package
  3. Create a new policy
  4. Add the Windows integration
  5. Deploy the Elastic-Agent to a Windows host
  6. Check the following dashboards are working:
    • [Windows powershell] Overview
    • [Metrics Windows] Services
    • [Windows AppLocker] Audited and Blocked Applications

Related issues

## Screenshots

@belimawr belimawr requested review from a team as code owners August 13, 2024 15:20
@belimawr belimawr requested review from rdner and mauri870 August 13, 2024 15:20
@andrewkroh andrewkroh added Integration:windows Windows Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team [elastic/elastic-agent-data-plane] Team:Security-Windows Platform Security Windows Platform Team [elastic/sec-windows-platform] labels Aug 13, 2024
@elasticmachine
Copy link

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@elasticmachine
Copy link

Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform)

@pierrehilbert pierrehilbert requested review from leehinman and removed request for mauri870 August 13, 2024 15:33
This commit sets typeMigrationVersion to the version that was required
before the update to package spec v3
belimawr and others added 2 commits August 15, 2024 09:31
Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Field updates and manifest LGTM. I did not review the dashboards.

@andrewkroh andrewkroh added the enhancement New feature or request label Aug 19, 2024
conditions:
kibana:
version: "^8.8.0"
version: "^8.14.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any chance we can go earlier?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to back to 8.8, but other things broke, not even 8.10.1 worked :/

So I just let the one that was working.

@@ -6,6 +6,8 @@
name: destination.port
- external: ecs
name: dns.answers
type: object
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we get rid of the whole ecs.yml file and use the ecs dynamic mappings?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure.

I prefer to have explicit mapping to avoid any malformed data from creating the wrong mapping. Anyways I'm open to look into the dynamic mappings.

Update the ingest pipelines so the fields comply with ECS. Most of the
updates are transforming strings into arrays and some updating the
fields added to comply with ECS.
Updating the sample_event.json files fixes the static tests, the
changes in the README are made by the build process.
@elasticmachine
Copy link

🚀 Benchmarks report

Package windows 👍(4) 💚(2) 💔(3)

Expand to view
Data stream Previous EPS New EPS Diff (%) Result
applocker_exe_and_dll 5076.14 4255.32 -820.82 (-16.17%) 💔
applocker_packaged_app_execution 21739.13 6944.44 -14794.69 (-68.06%) 💔
sysmon_operational 3802.28 3125 -677.28 (-17.81%) 💔

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

History

@belimawr belimawr requested a review from leehinman August 30, 2024 18:55
@andrewkroh andrewkroh added the dashboard Relates to a Kibana dashboard bug, enhancement, or modification. label Aug 30, 2024
@belimawr belimawr merged commit 930efbc into elastic:main Sep 3, 2024
5 checks passed
@belimawr belimawr deleted the update-windows-integration-package-spec-v3 branch September 3, 2024 19:45
@elasticmachine
Copy link

Package windows - 2.0.0 containing this change is available at https://epr.elastic.co/search?package=windows

@maggieghamry
Copy link

Just as a head's up, it appears that as of this PR (confirmed in ESS and On-Prem), all Powershell event dashboards are now empty) after upgrading to 2.0.0 and above. Is there already an issue to capture this?

@belimawr
Copy link
Contributor Author

belimawr commented Oct 9, 2024

Just as a head's up, it appears that as of this PR (confirmed in ESS and On-Prem), all Powershell event dashboards are now empty) after upgrading to 2.0.0 and above. Is there already an issue to capture this?

I don't think so, at least I could not find one. This could have been caused by this PR, could you open an issue with details about the environment and how reproduce and test?

@pierrehilbert
Copy link
Contributor

Looks like we have an issue: elastic/elastic-agent#5746 (comment)

@belimawr
Copy link
Contributor Author

Looks like we have an issue: elastic/elastic-agent#5746 (comment)

Are you sure this is the same issue @maggieghamry described? Maybe you pasted the wrong link?

My understanding of the issue described by @maggieghamry is that the dashboard is not showing any data, but the agent is healthy.

@maggieghamry do you see any errors/unhealthy agents? Is new data not appearing in the dashboard or does the dashboard just stopped working even with data from the previous version of the agent present in the cluster?

@maggieghamry
Copy link

maggieghamry commented Oct 10, 2024

@belimawr I'm not sure it is the same issue, but we confirmed by testing on the last functional version (1.47.0) - after upgrading (you can test on-prem or ESS) to 2.0.0 or above, attempting to access the Powershell Dashboards, they are all empty with only workaround at this time being to downgrade or rollback for now.

harnish-elastic pushed a commit to harnish-elastic/integrations that referenced this pull request Feb 4, 2025
---------

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard Relates to a Kibana dashboard bug, enhancement, or modification. enhancement New feature or request Integration:windows Windows Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team [elastic/elastic-agent-data-plane] Team:Security-Windows Platform Security Windows Platform Team [elastic/sec-windows-platform]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate windows integration to package spec v3
6 participants