Agent Release Notes¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
See Alation Cloud Service Compatibility for information about which versions of Alation Cloud Service are supported by each version of the Agent. To get the latest Alation Agent features and fixes, we recommend upgrading to the latest version of the Alation Agent that’s compatible with your version of Alation Cloud Service.
Polling Mode UI¶
We’ve made some improvements in the Alation UI to help you understand when an Agent is in polling mode and how that could affect your connection:
The Agent Dashboard indicates whether the Agent is in polling mode.
When viewing connector details on the Connector Dashboard, you can see whether the connector is on an Agent that is in polling mode.
When testing RDBMS data source connections on the data source settings page, you can see whether the data source is connected through an Agent that is in polling mode.
The Alation Agent now supports connecting to Alation Cloud Service via polling mode.
Support for More Operating Systems¶
The Alation Agent now officially supports more operating systems:
Red Hat 9
For a complete list of supported operating systems, see the Agent system requirements.
Diagnostic Tool Improvements¶
The built-in diagnostic tool now checks that /etc/hosts is configured correctly. A missing or incorrect /etc/hosts file can disrupt the connection between Alation Cloud Services and the Alation Agent.
Is your Agent in a disconnected state? We’ve added a new diagnostic tool to the Agent that will help you troubleshoot connectivity issues. See the Troubleshooting topic for details on working with the diagnostic tool.
We fixed an issue where the Agent was failing to close old network connections when establishing failover connections to Alation Cloud Service.
The Alation Agent now establishes multiple failover connections to Alation Cloud Service for improved uptime and performance.
Support for Basic Authentication with Proxy¶
The Alation Agent now works with HTTP CONNECT proxies that require basic authentication. On the Agent machine, edit the /etc/hydra/hydra.toml file to include the following line:
web_proxy = "<username>:<password>@<proxy-address>:<proxy-port>"
Replace the parts in angle brackets with the appropriate information for your proxy.
See the Agent installation instructions for more details on configuring the Agent to work with a proxy.
We fixed an issue where the Agent could sometimes report an ERROR.E1000, which would prevent connectors from being installed. Upgrading to version 188.8.131.528 resolves this issue.
The Aalation Agent now supports Compose connections to on-premise data sources. This support includes:
Query execution in Compose
Excel live reports
Compose Compatibility with the Agent
In order to use Compose with the Alation Agent, you must:
Be on Alation Cloud Service version 2022.4 or later.
Have Alation Agent version 184.108.40.2068 or newer installed. Agent version 220.127.116.115 does not support Compose.
Have a supporting version of the relevant connector installed on the Agent. See the documentation for individual OCF connectors to find out if a particular connector can connect to Compose through the Alation Agent.
Multiple Agent Installations¶
Alation now supports multiple Alation Agent installations per cloud instance. Multiple Agents may be required if data sources are in different geographical locations, network segments, or security zones. A Server Admin for a cloud instance can now install Alation Agent multiple times to enable connection to on-premise data sources from the catalog.
Users can now delete an Agent even when the certificate is revoked.
The default port of 80 for
web_proxyis now honored by the Agent. Previously port 80 was incorrectly ignored and defaulted to 3128.