Monitor SFTP server availability and performance using synthetic checks.
This ActiveGate extension connects to a remote host and offers insights into the availability and performance of SFTP connections. The gathered data is transmitted to Dynatrace as a third-party synthetic test, enabling comprehensive analysis of outages and performance trends over time.
| Item | Description |
|---|---|
| IP or hostname of SFTP server | The IP or hostname of the SFTP server |
| Port | The SFTP server port |
Allows the extension to create external synthetic tests and post results to the test.
Use the local ActiveGate for synthetic test ingest. This option simplifies the extension's configuration by ingesting the synthetic events on the ActiveGate on which the extension is running.
URL of the Dynatrace API. Examples: abc123.dynatrace-managed.com/e/d22e9814-d46d-4b11-8ba0-6f76708e385f, abc1234.live.dynatrace.com.
API Token with access to create synthetic tests. Create a token with the ExternalSyntheticIntegration scope.
Configure which tests the extension should run.
Test read: If enabled, the extension attempts to read the contents of the directory and record the time it takes to perform this check.
Test put: If enabled, the extension attempts to upload the file provided in the Local file to upload parameter. The extension records the amount of time it takes to perform this test.
Test file processing: Verify that files are being processed as expected. Some SFTP servers run batch jobs or virus scans on files in SFTP directories. These processes temporarily rename files for further processing. This feature monitors files that have been renamed with a specific file suffix and ensures that their processing job is completed within a defined time frame.
File suffix: File suffix that indicates processing is taking place. For example, pending.
File age: Age in minutes that indicates a file failed to be processed.
Provide optional file paths to allow the extension to test SFTP read and upload.
Remote directory: Enter remote directory for read and put tests.
Local file to upload (under 100KB): Local file path. A file path on the ActiveGate that is accessible to the extension. Required for processing test.
Credentials for the SFTP user.
Use Credential Vault: Optionally, store user name and password in the Credential Vault. If chosen, select the appropriate credential from the dropdown menu.
User name: If the Credential Vault is not used, enter user name here.
Password: If the Credential Vault is not used, enter password here.
Connect via proxy: If enabled, connect to the SFTP server via a proxy.
HTTP Proxy Host:Port: If you use a proxy to communicate externally, enter the host:port.
HTTP Proxy User: If using Basic Auth to HTTP proxy, enter the username.
HTTP Proxy Password: If using Basic Auth to HTTP proxy, enter the password.
If the connection to the SFTP server requires a security key, provide the details here.
Use Credential Vault: Optionally, store the key file in the Credential Vault. If chosen, select the appropriate credential from the dropdown.
Location of key file: Add the full path to key on the ActiveGate.
Enable detailed logging on the host running the extension.
By default, logs are found on Linux hosts at /var/log/dynatrace/oneagent/extensions/datasources and on Windows hosts at C:\ProgramData\dynatrace\oneagent\log\extensions\datasources.
Once the extension is successfully running, you can explore tests from the Synthetic menu. These are automatically created using the endpoint's hostname and port.
Dynatrace automatically signals outages, and in-depth metrics are available, as for other synthetic tests. These can be found easily by typing synthetic.external in the Metrics menu.
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|