-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat(outputs.prometheus_client): Support vsock listen #6382 #14108
Conversation
Thanks so much for the pull request! |
e0929ce
to
cf7fc7b
Compare
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.
Thank you very much for tackling this old issue @jeffrey4l! Just one minor comment... Furthermore, I wanted to ask if you can also provide a unit-test for the vsock case!?
} | ||
return net.Listen("tcp", p.Listen) | ||
return nil, errors.New("Unknow scheme") |
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.
Error messages should start with a lower-case letter... (+typo fix)
return nil, errors.New("Unknow scheme") | |
return nil, errors.New("unknown scheme") |
Thanks for the PR. Sven left a comment above. In addition to that, would you be willing to write a unit test? Thanks! |
sure. will do later |
do yo have any idea how to test this? for the vsock, when listen on the host, it only can be connected from guest (qemu virtual machine). So i can listen on the vsock, but there is no way test it through real connect. |
@jeffrey4l does that somehow work with a container? If so, check using |
@srebhan no, it only works between host and qemu guest vm. ie listen on the host and connect from the qemu guest vm. or vice versa |
@jeffrey4l then I think we are out of luck for a unit-test. Thanks for clarifying! Can you please fix the merge conflicts and fix the two lines I commented on above!? After that I'm fine with the PR... |
69f1611
to
d8f0a9d
Compare
…6382) usage: listen = "vsock://:9273"
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
@srebhan pr is ready for review. |
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 for your contribution @jeffrey4l!
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.
Thank you!
* master: fix(inputs.win_perf_counter): Do not rely on returned buffer size (influxdata#14241) feat(inputs.modbus): Add support for string-fields (influxdata#14145) chore(deps): Bump cloud.google.com/go/storage from 1.30.1 to 1.34.1 (influxdata#14253) chore(deps): Bump github.com/rabbitmq/amqp091-go from 1.8.1 to 1.9.0 (influxdata#14252) chore(deps): Bump github.com/hashicorp/consul/api from 1.25.1 to 1.26.1 (influxdata#14251) chore(deps): Bump github.com/aws/aws-sdk-go-v2/service/cloudwatchlogs from 1.23.5 to 1.26.0 (influxdata#14249) fix(config): Fix comment removal in TOML files (influxdata#14240) feat(outputs.prometheus_client): Support listen on vsock (influxdata#14108) fix(inputs.mqtt_consumer): Resolve could not mark message delivered (influxdata#14243) chore(linters): Fix findings found by testifylint for Windows and enable it. (influxdata#14238) feat(migrations): Add option migration for inputs.nats_consumer (influxdata#14234) feat(migrations): Add option migration for inputs.mqtt_consumer (influxdata#14233) test(inputs.jolokia2_agent): Sort metrics as order is not consistent (influxdata#14227)
This is particial resolved the issue #6382