-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
New component: SSH Receiver #14312
Comments
@nslaughter thanks for proposing the component, i'm happy to sponsor it. Instead of a separate How does the test for sftp work? Does it require a file transfer to confirm it works? |
Thanks, @codeboten.
|
The goals and capabilities have remained the same. However, the implementation changed (a) to fit the networking patterns of the collector and (b) provide metrics in a way more fit with latest views of maintainers. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
The purpose and use-cases of the new component
Purpose: To monitor the availability and performance of SSH endpoints.
Use case: Methods of monitoring SSH host availability can either use the programs on the host or run as clients. This proposal is for monitoring as a client which can provide less information, but it doesn't require ownership of the host or any additional permissions. It performs simple checks by connecting to the host to validate it's available. Additionally, a common use of SSH is for file transfer over SFTP, which can be checked in the same way.
Example configuration for the component
Telemetry data types supported
Gauges
ssh_availability: 1/0 (up/down)
ssh_connection_time: (ms)
sftp_availability: 1/0 (up/down)
sftp_connection_time: (ms)
Is this a vendor-specific component?
Sponsor (optional)
@codeboten
Additional context
No response
The text was updated successfully, but these errors were encountered: