Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Correctly format the path to read data from npipe. (elastic#15997)
This is not a fix for elastic#15832 this will be tackle in another PR. When http+npipe:// scheme were initially parsed by the url parser of metric the generated PATH wasn't correctly setup up. So I've fixed the parsing and the tests. Now to test the behavior on Windows you will need a beat that expose metrics over npipes, you can do so with a configuration like this. ```yaml metricbeat.modules: - module: system output.console: ~ http.enabled: true http.host: \\.\pipe\custom ```yaml After you can start a Metricbeat instance with the beat modules to collect the metric information. ```yaml metricbeat.modules: - module: beat hosts: http+npipe://./pipe/custom metricsets: - stats - state output.console: ~ ``` If you start metricbeat with the `-e -d "*"` flags this will output any metrics fetched from the running beat instance. Fixes: elastic#15938 (cherry picked from commit 75ddc22)
- Loading branch information