Downloads:
279,132
Downloads of v 0.14.0:
5,049
Last Update:
08 Sep 2020
Package Maintainer(s):
Software Author(s):
- Martin Lindhe
- Calle Pettersson
Tags:
prometheus-windows-exporter.install prometheus windows exporter admin monitoring- Software Specific:
- Software Site
- Software Source
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Prometheus Windows exporter (MSI Installer)
This is not the latest version of Prometheus Windows exporter (MSI Installer) available.
- 1
- 2
- 3
0.14.0 | Updated: 08 Sep 2020
- Software Specific:
- Software Site
- Software Source
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
279,132
Downloads of v 0.14.0:
5,049
Maintainer(s):
Software Author(s):
- Martin Lindhe
- Calle Pettersson
Prometheus Windows exporter (MSI Installer) 0.14.0
This is not the latest version of Prometheus Windows exporter (MSI Installer) available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Martin Lindhe, Calle Pettersson. The inclusion of Martin Lindhe, Calle Pettersson trademark(s), if any, upon this webpage is solely to identify Martin Lindhe, Calle Pettersson goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Prometheus Windows exporter (MSI Installer), run the following command from the command line or from PowerShell:
To upgrade Prometheus Windows exporter (MSI Installer), run the following command from the command line or from PowerShell:
To uninstall Prometheus Windows exporter (MSI Installer), run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download prometheus-windows-exporter.install --internalize --version=0.14.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade prometheus-windows-exporter.install -y --source="'INTERNAL REPO URL'" --version="'0.14.0'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade prometheus-windows-exporter.install -y --source="'INTERNAL REPO URL'" --version="'0.14.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install prometheus-windows-exporter.install
win_chocolatey:
name: prometheus-windows-exporter.install
version: '0.14.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'prometheus-windows-exporter.install' do
action :install
source 'INTERNAL REPO URL'
version '0.14.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller prometheus-windows-exporter.install
{
Name = "prometheus-windows-exporter.install"
Version = "0.14.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'prometheus-windows-exporter.install':
ensure => '0.14.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was approved by moderator gep13 on 09 Sep 2020.
Prometheus exporter for Windows machines.
Note: This package supersedes the "prometheus-wmi-exporter.install" package. The exporter will be renamed, and this package has been renamed to match. This package is being created now provide for a smoother transition.
Package parameters
The following package parameters can be set:
EnabledCollectors
- A comma-separated list of collectors to enable in the exporter. Options and defaults in "Collectors" section below.ListenAddress
- The IP address to bind to. Defaults to 0.0.0.0.ListenPort
- The port to bind to. Defaults to 9182.MetricsPath
- The path at which to serve metrics. Defaults to/metrics
.TextFileDir
- Specifies a directory for the textfile collector (equivalent to the--collector.textfile.directory
flag).ExtraFlags
- Allows passing full CLI flags. Defaults to an empty string.
These parameters can be passed to the installer with the use of --params
.
For example: --params '"/EnabledCollectors:cpu,dns,iis /ListenPort:9182"'
.
Collectors
A table of the provided collectors, including those enabled by default, is available at the project page here:
https://github.com/prometheus-community/windows_exporter/blob/v0.14.0/README.md#collectors
More Information
For more information, see the project README:
https://github.com/prometheus-community/windows_exporter/blob/v0.14.0/README.md
$ErrorActionPreference = 'Stop';
$packageName = 'prometheus-windows-exporter.install'
$softwareName = 'windows_exporter*'
$installerType = 'MSI'
$silentArgs = '/quiet /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
$validExitCodes = @(0)
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName
if ($key.Count -eq 1) {
$key | % {
$file = "$($_.UninstallString)"
if ($installerType -eq 'MSI') {
$silentArgs = "$($_.PSChildName) $silentArgs"
$file = ''
}
Uninstall-ChocolateyPackage -PackageName $packageName `
-FileType $installerType `
-SilentArgs "$silentArgs" `
-ValidExitCodes $validExitCodes `
-File "$file"
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$key.Count matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $_.DisplayName"}
}
Log in or click on link to see number of positives.
- prometheus-windows-exporter.install.0.14.0.nupkg (df14687bf28c) - ## / 60
- windows_exporter-0.14.0-amd64.msi (aaad64650a4b) - ## / 57
- windows_exporter-0.14.0-386.msi (e33cae723252) - ## / 59
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
-
- chocolatey-core.extension (≥ 1.1.0)
Ground Rules:
- This discussion is only about Prometheus Windows exporter (MSI Installer) and the Prometheus Windows exporter (MSI Installer) package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Prometheus Windows exporter (MSI Installer), or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.