-
Notifications
You must be signed in to change notification settings - Fork 515
[Prometheus] Add username, password, and SSL related fields for query dataset #13969
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
Conversation
979d819 to
90d90fd
Compare
|
@mykola-elastic : Thanks for the PR. |
| - name: ssl.verification_mode | ||
| type: text | ||
| title: SSL Verification Mode | ||
| description: SSL verification mode. See [documentation](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-ssl.html#client-verification-mode) for details. |
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.
Lets use the corresponding fleet links instead of beats here
https://www.elastic.co/guide/en/fleet/current/elastic-agent-ssl-configuration.html
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.
Thanks, I added the new links
Hello @ishleenk17 . Thanks for the review! I copied the fields from the https://github.com/elastic/integrations/blob/main/packages/prometheus/data_stream/collector/agent/stream/stream.yml.hbs#L18-L42 I have tested that the Shall I test the SSL as well? If yes, do we have any easy way to test SSL (a preconfigured Prometheus instance with SSL certs which can be used for testing)? I think I shall be able to test it using locally generated(self-signed) certificates, I will get back to you when it is done |
|
@ishleenk17 I've tested (successfully) using self-signed certificates. Specifically the fields |
|
I've added an issue for the Metricbeat's error handling elastic/beats#44446 which is related to this PR |
This testing shall suffice @mykola-elastic. |
ishleenk17
left a comment
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.
Looks good!
Thanks
💚 Build Succeeded
History
|
|
|
Package prometheus - 1.24.0 containing this change is available at https://epr.elastic.co/package/prometheus/1.24.0/ |
* main: (42 commits) [jamf_pro] Fix `flattened` field types for non-object values (elastic#13985) [Netskope Alerts] Add text multi-field to netskope.alerts.breach.description field (elastic#13977) zscaler_zia: add strict field template mode for tcp and http_endpoint input data streams (elastic#13904) apm: Add config for tail-based sampling discard on write (elastic#13950) [CI] Add dev/coverage into backport script (elastic#13987) Update configuration updatecli for 8.x snapshot (elastic#13981) [Prometheus] Add username, password, and SSL related fields for query dataset (elastic#13969) o365: Ignore failures in rename processors for organization fields (elastic#13983) aws.firewall: Document ingested log types of AWS Network Firewall (elastic#13978) mimecast: resolve field data type conflicts between data streams (elastic#13825) [Infoblox NIOS] Handle the parsing of IPv6 address (elastic#13947) [Cribl] Fix handling of metric event type (elastic#13930) zscaler_zpa: fix handling of multiple remote IPs, and event categorisation (elastic#13755) Adding agentless deployment to the sublime security integration (elastic#13963) [integration/system] add use_performance_counters in system integration (elastic#13150) crowdstrike,m365_defender,microsoft_defender_{cloud,endpoint},sentinel_one: normalise severity handling (elastic#13955) [forgerock] Map `forgerock.response.elapsedTime` as a long not a date (elastic#13959) github: squelch errors from pagination ends (elastic#13965) cisco_secure_endpoint: squelch errors from pagination ends (elastic#13964) [Cloud Security] Cloud Asset Inventory: fixed cloud formation URL (elastic#13971) ...
* feature/use-google-secrets: (43 commits) use -ci account [jamf_pro] Fix `flattened` field types for non-object values (#13985) [Netskope Alerts] Add text multi-field to netskope.alerts.breach.description field (#13977) zscaler_zia: add strict field template mode for tcp and http_endpoint input data streams (#13904) apm: Add config for tail-based sampling discard on write (#13950) [CI] Add dev/coverage into backport script (#13987) Update configuration updatecli for 8.x snapshot (#13981) [Prometheus] Add username, password, and SSL related fields for query dataset (#13969) o365: Ignore failures in rename processors for organization fields (#13983) aws.firewall: Document ingested log types of AWS Network Firewall (#13978) mimecast: resolve field data type conflicts between data streams (#13825) [Infoblox NIOS] Handle the parsing of IPv6 address (#13947) [Cribl] Fix handling of metric event type (#13930) zscaler_zpa: fix handling of multiple remote IPs, and event categorisation (#13755) Adding agentless deployment to the sublime security integration (#13963) [integration/system] add use_performance_counters in system integration (#13150) crowdstrike,m365_defender,microsoft_defender_{cloud,endpoint},sentinel_one: normalise severity handling (#13955) [forgerock] Map `forgerock.response.elapsedTime` as a long not a date (#13959) github: squelch errors from pagination ends (#13965) cisco_secure_endpoint: squelch errors from pagination ends (#13964) ...
… dataset (elastic#13969) * [Prometheus] Add username, password, and SSL related fields for query dataset * use corresponding fleet links instead of beats




Proposed commit message
[Prometheus] Add username, password, and SSL related fields for query dataset
Checklist
changelog.ymlfile.Related issues
querydataset #13751Note
Added fields work well for the case of successful authorization.
When the auth information is wrong, the error messages look the following way:
https://github.com/elastic/beats/blob/main/metricbeat/module/prometheus/collector/collector.go#L154
https://github.com/elastic/beats/blob/main/metricbeat/helper/prometheus/prometheus.go#L107
https://github.com/elastic/beats/blob/main/metricbeat/module/prometheus/query/query.go#L86
The error message is misleading and can be fixed by editing the code of Metricbeat