-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Use common host parser in vsphere module #26904
Conversation
Pinging @elastic/integrations (Team:Integrations) |
Oh I see this would be needed anyway, right? as the vsphere URL may actually need to be sanitized |
I thought about that, but what value would we use? With |
Yes, let's move the conversation to #26902 as it has more implications |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Use the common host parser builder to parse hosts defined in vsphere module configuration. Since #21022, sanitized URIs included in modules host data are used as `service.address`. vsphere did a custom parsing that didn't fill the sanitized URI and then `service.address` was not filled. (cherry picked from commit 68e9909)
Use the common host parser builder to parse hosts defined in vsphere module configuration. Since #21022, sanitized URIs included in modules host data are used as `service.address`. vsphere did a custom parsing that didn't fill the sanitized URI and then `service.address` was not filled. (cherry picked from commit 68e9909)
Use the common host parser builder to parse hosts defined in vsphere module configuration. Since #21022, sanitized URIs included in modules host data are used as `service.address`. vsphere did a custom parsing that didn't fill the sanitized URI and then `service.address` was not filled. (cherry picked from commit 68e9909) Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
) Use the common host parser builder to parse hosts defined in vsphere module configuration. Since #21022, sanitized URIs included in modules host data are used as `service.address`. vsphere did a custom parsing that didn't fill the sanitized URI and then `service.address` was not filled. (cherry picked from commit 68e9909) Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
* master: (61 commits) Add disk queue unit tests based on the queuetest package [Heartbeat] redact authorization headers from logger (elastic#26892) Expose custom process metrics (elastic#26912) [gcp/billing] always quote table name identifier (elastic#26870) Add Beats central management removal to BCs (elastic#26400) Add custom suffix to identifiers in filestream input when needed (elastic#26669) Update asa-ftd-pipeline.yml (elastic#26265) Use common host parser in vsphere module (elastic#26904) [automation] Update go release version 1.16.6 (elastic#26860) Skip flaky test: filestream and harvester group (elastic#26728) [Filebeat] Remove alias fields from Suricata and Traefik module mappings (elastic#26627) docs: apm-server.auth (elastic#26831) [Automation] Update elastic stack version to 8.0.0-2f008f4a for testing (elastic#26881) Clarify the scope of start/end multiline example (elastic#26786) [Heartbeat]: update Node.js version for synthetics (elastic#26867) [fix][httpjson] Fix incorrect key for template data (elastic#26848) [httpjson] Add value_type parameter to httpjson transforms (elastic#26847) [Heartbeat]: capture error from journey/end events (elastic#26781) [Winlogbeat] Fixes for wineventlog experimental api (elastic#26826) Set agent.id to Fleet Agent ID for each metric/log monitoring input (elastic#26776) ...
What does this PR do?
Use the common host parser builder to parse hosts defined in vsphere module configuration.
Why is it important?
Since #21022, sanitized URIs included in modules host data are used as
service.address
. vsphere did a custom parsing that didn't fill the sanitized URI and thenservice.address
was not filled.See #26902.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Run the
vsphere
module and check that documents contain aservice.address
field that corresponds to the sanitized (without passwords) configured host.Related issues
Use cases