Skip to content
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

Document username/password options for HTTP based modules #7134

Merged
merged 1 commit into from
May 23, 2018

Conversation

tsg
Copy link
Contributor

@tsg tsg commented May 18, 2018

This adds commented out username and password settings to most
of the config places where they are supported (this part is manual).
Since those configs are included in the docs, they also show up there.

This also adds a line in the docs that link to "HTTP specific settings"
(this part is automatised during make update).

Completes #4268 and closes #6493.

@tsg tsg added docs needs_backport PR is waiting to be backported to other branches. v7.0.0-alpha1 labels May 18, 2018
@tsg tsg requested a review from dedemorton May 18, 2018 09:42
@tsg tsg force-pushed the document_user_password_for_http_modules branch from 7969d63 to 29c7c92 Compare May 18, 2018 09:46
Copy link
Contributor

@exekias exekias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -200,3 +200,19 @@ A list of processors to apply to the data generated by the metricset.
See <<filtering-and-enhancing-data>> for information about specifying
processors in your config.

[float]
[[module-http-config-options]]
=== Standard HTTP config options
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should just copy SSL settings here too, as both things are supported by the same helper

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious what @dedemorton thinks of this. Perhaps a fragment that we include in both (or multiple) places?

Copy link
Contributor

@dedemorton dedemorton May 18, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tsg Thank you for doing this! Right now, I agree that the user experience is not ideal (there's a lot of jumping around to find the full list of config options). Rather than pointing to another topic, I'd prefer to use an include to pull in any common (shared) options. To make this work, we'll need to add an attribute to the docs for each module (something like :modulename: modulename) and then use that attribute in the ID for shared sections. Do you want me to do that? This has been low down on my to-do list for awhile; I can bump the priority.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...and looking at my notes, I see that the current design (pointing off to options) has resulted in problems for users in other areas (like not knowing that processors are valid in the config).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have this as a to-do item in a meta issue, but I've created a real issue to track the work: #7160

This adds commented out `username` and `password` settings to most
of the config places where they are supported (this part is manual).
Since those configs are included in the docs, they also show up there.

This also adds a line in the docs that link to "HTTP specific settings"
(this part is automatised during `make update`).

Completes elastic#4268 and closes elastic#6493.
@tsg tsg force-pushed the document_user_password_for_http_modules branch from 29c7c92 to 44231f2 Compare May 18, 2018 10:00
@exekias
Copy link
Contributor

exekias commented May 22, 2018

I'm ok with merging this one, we can find a long-term solution later on

@exekias exekias merged commit 0a85fce into elastic:master May 23, 2018
tsg added a commit to tsg/beats that referenced this pull request Jun 14, 2018
This adds commented out `username` and `password` settings to most
of the config places where they are supported (this part is manual).
Since those configs are included in the docs, they also show up there.

This also adds a line in the docs that link to "HTTP specific settings"
(this part is automatised during `make update`).

Completes elastic#4268 and closes elastic#6493.

(cherry picked from commit 0a85fce)
@tsg tsg added v6.3.1 and removed needs_backport PR is waiting to be backported to other branches. labels Jun 14, 2018
jsoriano pushed a commit that referenced this pull request Jun 26, 2018
… based modules (#7330)

Add commented out `username` and `password` settings to most
of the config places where they are supported (this part is manual).
Since those configs are included in the docs, they also show up there.

This also adds a line in the docs that link to "HTTP specific settings"
(this part is automatised during `make update`).

Completes #4268 and closes #6493.
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…or HTTP based modules (elastic#7330)

Add commented out `username` and `password` settings to most
of the config places where they are supported (this part is manual).
Since those configs are included in the docs, they also show up there.

This also adds a line in the docs that link to "HTTP specific settings"
(this part is automatised during `make update`).

Completes elastic#4268 and closes elastic#6493.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document http authentication for metricbeat http module
4 participants