-
Notifications
You must be signed in to change notification settings - Fork 219
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_exporter to v0.27.3 #1785
Conversation
Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
Hi, is this fix going to be released soon as 1.4.2?
Thank you. |
* Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> * Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> --------- Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> (cherry picked from commit 65b9f44)
@lukaszch we are planning a patch release containing this bugfix for the end of the week |
* Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> * Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> --------- Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
…SION file (#1828) * chore: bump yet-another-cloudwatch-exporter to v0.61.0 (#1690) * chore: bump yet-another-cloudwatch-exporter to v0.61.0 This bumps yet-another-cloudwatch-exporter to v0.61.0, which fixes [an issue with S3 metrics being reported as `NaN`](prometheus-community/yet-another-cloudwatch-exporter#728). Affected metrics have a value of `0` in the scraped prometheus metrics. With the update to v0.61.0, they are reported correctly. * fixup! chore: bump yet-another-cloudwatch-exporter to v0.61.0 JobLevelMetricFields has been removed with prometheus-community/yet-another-cloudwatch-exporter#1412 * fixup! chore: bump yet-another-cloudwatch-exporter to v0.61.0 * Update windows_exporter to v0.27.3 (#1785) * Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> * Update windows_exporter to v0.27.3 Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> --------- Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> * build(deps): bump webpack from 5.82.1 to 5.94.0 in /internal/web/ui (#1594) Bumps [webpack](https://github.com/webpack/webpack) from 5.82.1 to 5.94.0. - [Release notes](https://github.com/webpack/webpack/releases) - [Commits](webpack/webpack@v5.82.1...v5.94.0) --- updated-dependencies: - dependency-name: webpack dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * build(deps): bump rollup from 2.79.1 to 2.79.2 in /internal/web/ui (#1775) Bumps [rollup](https://github.com/rollup/rollup) from 2.79.1 to 2.79.2. - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](rollup/rollup@v2.79.1...v2.79.2) --- updated-dependencies: - dependency-name: rollup dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * 1687 otelcol.exporter.awss3 config fixes (#1791) * Address loki.process config reloads (#1809) * Fix logs cluster (#1716) * fix clustering for logs * Simplify code. * Add changelog. * Reorder changelog * Update VERSION --------- Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: morre <mmeyer@anaconda.com> Co-authored-by: Jan-Otto Kröpke <mail@jkroepke.de> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: cydergoth <cydergoth@gmail.com> Co-authored-by: Piotr <17101802+thampiotr@users.noreply.github.com> Co-authored-by: mattdurham <mattdurham@ppog.org>
Just installed 1.4.2 and getting same error runtime error: invalid memory address or nil pointer dereference |
@RABCbot could you please post the full stracktrace? |
runtime error: invalid memory address or nil pointer dereference goroutine 812 [running]: |
The stack you post does not match to the lines in v0.27.3. The stacktrace indicate that v0.27.2 is still in used. I guess you may hit this bug: #565, where the installer does not replaced the alloy binaries. Try to install 1.4.2 again. |
PR Description
Fixes #1744
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist