Troubleshooting issues in Alert

This page describes troubleshooting issues.

Azure authentication issues

If you get an error authenticating with Azure, try the following steps:

1. Click the Delete button in the global configuration for Azure in Alert.

2. Go to the Azure application that is used for the OAuth connection and revoke the connection.

3. Re-enter the values for the global configuration for Azure in Alert.

4. Click the Test Configuration to make sure the configuration is working and the issue is resolved.

To use the standard Alert login functionality (i.e. login as a user stored in the Alert database rather than an external system) when SAML is enabled, append the query parameter ?ignoreSAML=true to the Alert URL in the address bar.

 WARNING: Always be sure to secure the passwords of users created in Alert including the default Alert users (sysadmin, jobmanager, alertuser).

Alert Port issue related symptoms

The following issues are often caused by misconfiguring the server port when deploying Alert using the Helm files.

Issues

1. Incorrect link to the Alert server in emails

2. Connection problems with Azure Boards

3. Connection problems with SAML

4. Unable to reach the Swagger UI when using the link in the About Page

Solution(s):

1. Set the exposedNodePort in the Helm deployment files
   Alert can not determine the exposed public port that is used so this must be manually configured so that Alert can create correct URLs when referencing itself.

2. Change the forwardHeadersStrategy to "native"
   If using a proxy or load balancer, this helps Alert figure out the "public" URL used to access Alert when using the UI.