The failed-connection alarm is raised when a component in the Curity Identity Server fails to establish a connection against a remote host. This could be against a data source such as MySQL or LDAP, or an HTTP Service such as BankID or Duo.
The reason for the alarm can be a faulty configuration, faulty networking or a faulty remote service.
The severity is at least minor since parts of the system are already affected.
Immediate action is required. A connection to an external system has failed at least once. Immediate action is required if the state of the alarm is raised.
Fig. 8 Failed to connect against remote service
This alarm can be raised by two types of components in the Curity Identity Server.
Data Sources will raise the alarm if a connection cannot be established. However some data sources rely on HTTP clients for connections, such as the Scim and Json data sources. These will not raise this alarm, but will instead be listed as impacted resources when the Http Client raises the alarm.
HTTP clients will raise this alarm when a connection cannot be established. This is different from an established connection that returns an error, or failing to authenticate against the remote service.
The alarm is raised when the Curity Identity Server fails to establish connection to the remote host using the configured resource.
The alarm is cleared after a successful connection have been asserted against the remote host and a small amount of time without further issues has passed. This means that if the connection is flaky, the alarm will not be cleared until the condition is deemed stable.
No configuration options are available for this alarm type.