-
Notifications
You must be signed in to change notification settings - Fork 246
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 and lint discovery topics #2403
base: main
Are you sure you want to change the base?
Conversation
💻 Deploy preview available: https://deploy-preview-alloy-2403-zb444pucvq-vp.a.run.app/docs/alloy/latest/ |
Related issue #2411 |
- _`<USERNAME>`_: The username to use for authentication to the `remote_write` API. | ||
- _`<PASSWORD>`_: The password to use for authentication to the `remote_write` API. | ||
|
||
* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to. |
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.
Should these be alpha order?
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 thought about that.... right now that are all in the order they are encountered in the config file.
authorization | [authorization][] | Configure generic authorization to the endpoint. | no | ||
oauth2 | [oauth2][] | Configure OAuth2 for authenticating to the endpoint. | no | ||
basic_auth | [basic_auth][] | Configure `basic_auth` for authenticating to the endpoint. | no | ||
oauth2 | [oauth2][] | Configure OAuth 2.0 for authenticating to the endpoint. | no | ||
oauth2 > tls_config | [tls_config][] | Configure TLS settings for connecting to the endpoint. | 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.
Should this description somehow distinguish the purpose of the oauth2 > tls_config
vs higher level tls_config
?
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.
The descriptions in the Blocks tables are weak in a lot of places. This is something I think we could defer to a separate issue and revisit.
Created #2442 to track this
- _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to. | ||
- _`<USERNAME>`_: The username to use for authentication to the remote_write API. | ||
- _`<PASSWORD>`_: The password to use for authentication to the remote_write API. | ||
* _`<PROMETHEUS_REMOTE_WRITE_URL>`_: The URL of the Prometheus remote_write-compatible server to send metrics to. |
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.
Not going to mark each of these, but should this also be alpha order?
* _`<USERNAME>`_: The username to use for authentication to the remote_write API. | ||
* _`<PASSWORD>`_: The password to use for authentication to the remote_write API. | ||
|
||
{{< admonition type="note" >}} |
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.
Should the note be at the top of the example?
PR Description
Splitting Discovery updates into multiple PRs to make reviews a bit easier.
Changes include:
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist