New features and improvements in DPA

Last updated:

Send DPA alert notifications to PagerDuty or ServiceNow

You can use Platform Connect to connect DPA with SolarWinds Observability. When the connection is established, DPA alert notifications can be sent to third-party notification services that are configured in SolarWinds Observability. Currently, DPA supports sending alert notifications to PagerDuty and ServiceNow. For ServiceNow, only ITOM events are supported.

DPA users with subscription licenses are eligible to connect to SolarWinds Observability. Users doing a 14-day evaluation and users with temporary licenses (for a fixed term) are also eligible.

Platform Connect beta users

If you used the beta version of Platform Connect to connect DPA and SolarWinds Observability, the formatting of alert notifications from DPA has been improved in this release to make them easier to read, and additional information is included. The description includes the alert name, the database name, and the severity. Custom details include information about the alarm level, the alert description, and more.

Before upgrading from the Platform Connect beta version to the version provided with DPA 2024.3, complete the steps under Before you upgrade!

DPA can use the CyberArk LogonDomain value

In previous versions, if DPA was configured to use credentials stored in CyberArk, DPA ignored any value in the LogonDomain field of the CyberArk object. If a domain needed to be specified during authentication, it was specified in the UserName field, with the format DOMAIN_NAME\Username.

In DPA 2024.3 and later, a domain can be specified in either the LogonDomain field or the UserName field of the CyberArk object:

• If the LogonDomain field contains a value and the UserName field does not contain a backslash (\), DPA prepends the domain name and a backslash to the user name.

  For example, if CyberArk sends the following object, DPA prepends the LogonDomain value to the UserName value, and the value used for authentication is MYDOMAIN\MyUserName.

  {
      "Content": "ABCD123",
      "Folder": "Root",
      "LogonDomain": "MYDOMAIN",
      "Name": "testobject3",
      "UserName": "MyUserName",
      "Safe": "Test",
      "PasswordChangeInProcess": "False"
  }

• If the UserName field contains a backslash (\), DPA uses that value and ignores the LogonDomain field (if present).

  For example, if CyberArk sends the following object, DPA uses the value MYDOMAIN\MyUserName for authentication.

  {
      "Content": "ABCD123",
      "Folder": "Root",
      "Name": "testobject3",
      "UserName": "MYDOMAIN\MyUserName",
      "Safe": "Test",
      "PasswordChangeInProcess": "False"
  }

Additions to monitored instances and system requirements

DPA 2024.3 adds support for monitoring the following:

• The DPA repository database can be created on:

  • Oracle 23c
  • MySQL 8.3

• DPA can monitor the following database instances:

  • Oracle 23c
  • MySQL 8.3
  • PostgreSQL 16
  • EDB Postgres 16