-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Include description, product name and product version in Windows versions of Beats #15232
Labels
Comments
Pinging @elastic/siem (Team:SIEM) |
I opened a PR to add this info to .exe files in #16048. |
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Feb 25, 2020
This adds metadata to the Windows .exe files that the build produces. This makes our binaries a little more friendly to automation on Windows because you can check the version programmatically with ease. It also makes is easy for end user to inspect some details about the file from the file properties dialog in Windows. Closes elastic#15232 For example: ``` PS C:\vagrant\winlogbeat > (Get-Info .\winlogbeat.exe).VersionInfo | Format-List OriginalFilename : winlogbeat.exe FileDescription : Winlogbeat ships Windows event logs to Elasticsearch or Logstash. ProductName : Winlogbeat Comments : commit=8d6cf58f347579188d707421da6b70b2f66701ea CompanyName : Elastic FileName : C:\vagrant\winlogbeat\winlogbeat.exe FileVersion : 8.0.0 ProductVersion : 8.0.0 IsDebug : False IsPatched : False IsPreRelease : False IsPrivateBuild : False IsSpecialBuild : False Language : Language Neutral LegalCopyright : Copyright Elastic, License ASL 2.0 LegalTrademarks : PrivateBuild : SpecialBuild : FileVersionRaw : 8.0.0.0 ProductVersionRaw : 8.0.0.0 ```
andrewkroh
added a commit
that referenced
this issue
Feb 26, 2020
This adds metadata to the Windows .exe files that the build produces. This makes our binaries a little more friendly to automation on Windows because you can check the version programmatically with ease. It also makes is easy for end user to inspect some details about the file from the file properties dialog in Windows. Closes #15232 For example: ``` PS C:\vagrant\winlogbeat > (Get-Info .\winlogbeat.exe).VersionInfo | Format-List OriginalFilename : winlogbeat.exe FileDescription : Winlogbeat ships Windows event logs to Elasticsearch or Logstash. ProductName : Winlogbeat Comments : commit=8d6cf58f347579188d707421da6b70b2f66701ea CompanyName : Elastic FileName : C:\vagrant\winlogbeat\winlogbeat.exe FileVersion : 8.0.0 ProductVersion : 8.0.0 IsDebug : False IsPatched : False IsPreRelease : False IsPrivateBuild : False IsSpecialBuild : False Language : Language Neutral LegalCopyright : Copyright Elastic, License ASL 2.0 LegalTrademarks : PrivateBuild : SpecialBuild : FileVersionRaw : 8.0.0.0 ProductVersionRaw : 8.0.0.0 ```
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Mar 16, 2020
This adds metadata to the Windows .exe files that the build produces. This makes our binaries a little more friendly to automation on Windows because you can check the version programmatically with ease. It also makes is easy for end user to inspect some details about the file from the file properties dialog in Windows. Closes elastic#15232 For example: ``` PS C:\vagrant\winlogbeat > (Get-Info .\winlogbeat.exe).VersionInfo | Format-List OriginalFilename : winlogbeat.exe FileDescription : Winlogbeat ships Windows event logs to Elasticsearch or Logstash. ProductName : Winlogbeat Comments : commit=8d6cf58f347579188d707421da6b70b2f66701ea CompanyName : Elastic FileName : C:\vagrant\winlogbeat\winlogbeat.exe FileVersion : 8.0.0 ProductVersion : 8.0.0 IsDebug : False IsPatched : False IsPreRelease : False IsPrivateBuild : False IsSpecialBuild : False Language : Language Neutral LegalCopyright : Copyright Elastic, License ASL 2.0 LegalTrademarks : PrivateBuild : SpecialBuild : FileVersionRaw : 8.0.0.0 ProductVersionRaw : 8.0.0.0 ``` (cherry picked from commit 695b167)
andrewkroh
added a commit
that referenced
this issue
Mar 16, 2020
This adds metadata to the Windows .exe files that the build produces. This makes our binaries a little more friendly to automation on Windows because you can check the version programmatically with ease. It also makes is easy for end user to inspect some details about the file from the file properties dialog in Windows. Closes #15232 For example: ``` PS C:\vagrant\winlogbeat > (Get-Info .\winlogbeat.exe).VersionInfo | Format-List OriginalFilename : winlogbeat.exe FileDescription : Winlogbeat ships Windows event logs to Elasticsearch or Logstash. ProductName : Winlogbeat Comments : commit=8d6cf58f347579188d707421da6b70b2f66701ea CompanyName : Elastic FileName : C:\vagrant\winlogbeat\winlogbeat.exe FileVersion : 8.0.0 ProductVersion : 8.0.0 IsDebug : False IsPatched : False IsPreRelease : False IsPrivateBuild : False IsSpecialBuild : False Language : Language Neutral LegalCopyright : Copyright Elastic, License ASL 2.0 LegalTrademarks : PrivateBuild : SpecialBuild : FileVersionRaw : 8.0.0.0 ProductVersionRaw : 8.0.0.0 ``` (cherry picked from commit 695b167)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Windows version of different Beats has an .exe file that lacks info on Product name and Product version. See screenshot1.png. Also, the Beat service doesn't seem to have a Description like other services in Windows when looking at services.msc. See screenshot2.png.
The above would be great to have when scripting upgrades of Beats using for example powershell and you want to check which product version of the is file available. Apart from that this info would make it consistent with other .exe files and services in Windows.
The text was updated successfully, but these errors were encountered: