Amazon Redshift will no longer support the creation of new Python UDFs starting Patch 198.
Existing Python UDFs will continue to function until June 30, 2026. For more information, see the
blog post
Set the application name connection property
When you connect to Amazon Redshift, set the optional application name driver property. This property identifies which application or tool established each connection, which makes it easier to monitor, audit, and troubleshoot your Amazon Redshift environment.
The application name that you provide appears in the
application_name column of SYS_CONNECTION_LOG. You can
use it to do the following:
-
Track connection sources. Identify which applications, services, or tools connect to your cluster.
-
Troubleshoot performance. Correlate queries with the originating application to isolate performance issues.
-
Audit access. Understand application-level usage patterns across your data warehouse.
The following table shows how to set the application name for each Amazon Redshift driver.
| Driver | Property | Example |
|---|---|---|
| JDBC | ApplicationName |
jdbc:redshift:// |
| ODBC | ApplicationName |
Set ApplicationName=my-bi-tool in the DSN or
connection string. |
| Python | application_name |
redshift_connector.connect(...,
application_name='my-data-catalog') |
For more information about the application name property for each driver, see the following:
JDBC: ApplicationName
ODBC: ApplicationName
Python: application_name
Note
Use a descriptive, consistent naming convention for application names, such as
(for example, team-service-environmentquicksight-analytics-dashboard-prod). This approach makes it
easier to filter and analyze SYS_CONNECTION_LOG data.