A critical dashboard that is used for outages has stopped working.
Release : 20.4
You can add your own data sources to dashboards per this document. If they are not configured correctly, this will cause dashboards to timeout and no longer work.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-4/configuring-and-viewing-monitoring-data/the-dashboard-portlet/create-and-assign-the-data-source-for-a-widget.html
Removing these or correcting them if needed will resolved the issue.
Delete or correct the <jdbc> section from the dashboard section of the wasp.cfg file, you may use raw configuration or manually remove or edit the file, then restart the wasp probe.
<jdbc>
<3>
jdbc_driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
name = jdbc/nis
jdbc_username = <redacted>
jdbc_url = jdbc:sqlserver://;serverName=<redacted>141;databaseName=NimsoftSLM;instanceName=<redacted>;applicationName=/<redacted>/PrimaryHub/<redacted>/dap
jdbc_password = <redacted>
</3>
<2>
jdbc_driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
name = jdbc/oracle
jdbc_username = <redacted>
jdbc_url = jdbc:sqlserver://;serverName=<redacted>141;databaseName=NimsoftSLM;instanceName=<redacted>;applicationName=/<redacted>/PrimaryHub/<redacted>/dap
jdbc_password = <redacted>
</2>
<1>
jdbc_driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
name = jdbc/dap
jdbc_username = <redacted>
jdbc_url = jdbc:sqlserver://;serverName=<redacted>141;databaseName=NimsoftSLM;instanceName=<redacted>;applicationName=/<redacted>/PrimaryHub/<redacted>/dap
jdbc_password = <redacted>
</1>
</jdbc>