-
Notifications
You must be signed in to change notification settings - Fork 380
Update windows exporter dependency to v0.31.1 #4037
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
base: main
Are you sure you want to change the base?
Conversation
💻 Deploy preview available: |
@@ -1,6 +1,6 @@ | |||
prometheus.remote_write "metrics_default" { | |||
endpoint { | |||
name = "default-b174ee" | |||
name = "default-04b53d" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is broken on main, probably from prom3.4 update.
@@ -18,7 +18,7 @@ prometheus.scrape "metrics_name_jobName" { | |||
|
|||
prometheus.remote_write "metrics_name" { | |||
endpoint { | |||
name = "name-b174ee" | |||
name = "name-04b53d" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is broken on main, probably from prom3.4 update.
| `exclude` | `string` | Regular expression of processes to exclude. | `"^$"` | no | | ||
| `include` | `string` | Regular expression of processes to include. | `"^.+$"` | no | | ||
|
||
The `counter_version` may be `0`, `1`, or `2`. A value of `0` uses the latest available (currently V2), the other values specify which version of the process collector to utilize. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the docs it's not clear what the difference in the versions is. Also, do you think it makes sense to default to v1 so that there are no breaking changes? And to open a "breaking change" Alloy GitHub issue for us to switch for v2 for Alloy v2? Is v1 going to be removed from the upstream exporter soon? If it's due to be removed soon, then we'll need to switch users to v2 sooner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It shouldn't be a breaking change, just an underlying implementation change, but I'll see if I can make some more clear documentation.
Makefile
Outdated
@@ -125,7 +125,8 @@ GO_LDFLAGS := -X $(VPREFIX).Branch=$(GIT_BRANCH) \ | |||
-X $(VPREFIXSYNTAX).Version=$(VERSION) \ | |||
-X $(VPREFIX).Revision=$(GIT_REVISION) \ | |||
-X $(VPREFIX).BuildUser=$(shell whoami)@$(shell hostname) \ | |||
-X $(VPREFIX).BuildDate=$(shell date -u +"%Y-%m-%dT%H:%M:%SZ") | |||
-X $(VPREFIX).BuildDate=$(shell date -u +"%Y-%m-%dT%H:%M:%SZ") \ | |||
-ld64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this do? Why is it necessary?
docs/sources/reference/components/prometheus/prometheus.exporter.windows.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/prometheus/prometheus.exporter.windows.md
Outdated
Show resolved
Hide resolved
This reverts commit da33ae2.
The `textfile` collector is currently configured with the `text_file` block. | ||
To be consistent with the `textfile` collector name, the `text_file` block will be deprecated in a future release and replaced with a `textfile` block. | ||
For backwards compatibility, the `textfile` collector can also be configured with the undocumented `text_file` block. | ||
It is identical to the `textfile` block, and will be removed in a future release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we should leave the text_file
block in the docs, but marked as deprecated until it's actually removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm open to it, I chose this approach as it pushes users towards the corrected block name but they can still find the block if they're searching through the docs for text_file.
Co-authored-by: Paulin Todev <[email protected]>
Co-authored-by: Paulin Todev <[email protected]>
@@ -69,11 +69,11 @@ You can use the following blocks with `prometheus.exporter.windows`: | |||
| [`smb`][smb] | Configures the `smb` collector. | no | | |||
| [`smtp`][smtp] | Configures the `smtp` collector. | no | | |||
| [`tcp`][tcp] | Configures the `tcp` collector. | no | | |||
| [`text_file`][text_file] | Configures the `textfile` collector. | no | | |||
| [`textfile`][textfile] | Configures the `textfile` collector. | no | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [`textfile`][textfile] | Configures the `textfile` collector. | no | | |
| [`text_file`][text_file] | (Deprecated: use `textfile` instead) Configures the `textfile` collector. | no | | |
| [`textfile`][textfile] | Configures the `textfile` collector. | no | |
We could document like this (as used elsewhere in the component docs - eg: in otelcol.connector.spanmetrics
). We are a little inconsistent with how we document deprecated args and blocks. I just picked the style that provides the most useful information.
For backwards compatibility, the `textfile` collector can also be configured with the undocumented `text_file` block. | ||
It is identical to the `textfile` block, and will be removed in a future release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For backwards compatibility, the `textfile` collector can also be configured with the undocumented `text_file` block. | |
It is identical to the `textfile` block, and will be removed in a future release. | |
{{< admonition type="caution" >}} | |
Starting with v1.11, the `text_file ` block is deprecated. | |
It will be removed in a future release. | |
Use the `textfile` block to configure the `textfile` collector. | |
{{< /admonition >}} |
Something like this to follow the advice here: https://grafana.com/docs/writers-toolkit/write/deprecate-remove/ (assuming the deprecation happens in 1.11?
PR Description
Updating the windows exporter dependency, again. A few more breaking changes, a few upgrades, and a few panic fixes.
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist