Since you are responsible for monitoring your applications, you can subscribe to receive a variety of different alerts regarding the health of your network. You can also work with your Ping Identity support teams to customize the alerts you receive and display them on Kibana dashboards.
Some of the most common PingFederate alerts and PingDirectory alerts are listed and described here.
PingFederate alerts
If more than 1 error occurs within 1 minute, alerts will be sent to those who subscribe to them. Alerts that PingFederate administrators often subscribe to include:
| Error alerts | Description |
|---|---|
| Fatal or critical errors | These errors were not discovered by other filters and likely require immediate attention. |
| Connectivity errors | These errors can occur for a variety of reasons and often indicate that cluster
members cannot communicate with components, either within or outside
of PingOne Advanced Services, or with each
other. PingFederate connectivity alerts are:
|
| Authentication flow errors | These errors indicate that the authentication flow contains
errors, which are often HandleAuthNRequest
errors. PingFederate authentication flow alerts are:
|
| Invalid action errors | These errors indicate that a large number of unexpected invalid
calls or actions were detected. The PingFederate invalid action
error is:
|
| Decoding errors | These errors indicate that a large number of token decoding
errors were detected. The PingFederate decoding error is:
|
PingDirectory alerts
If more than 1 error occurs within 1 minute, alerts will be sent to those who subscribe to them. Alerts that PingDirectory administrators often subscribe to include:
| Error alerts | Description |
|---|---|
| Fatal or critical errors | These errors were not discovered by other filters and likely
require immediate attention. The PingDirectory critical error is:
|
| General errors | These errors indicate that issues within the application might
negatively affect the user experience. PingDirectory general
alerts are:
|
| Connectivity errors | These errors can occur for a variety of reasons and often indicate that cluster
members cannot communicate with components, either within or outside
of PingOne Advanced Services, or with each
other. The PingDirectory connectivity error is:
|
| Replication errors | These errors indicate that data consistency issues exist.
PingDirectory replication alerts are:
|
| Performance errors | These errors indicate that performance has fluctuated more than
it normally does. The PingDirectory performance alert is:
|
| Garbage collection errors | These errors indicate that garbage collection processes are
occurring more frequently, or are taking longer than expected.
The PingDirectory garbage collection filter alert is:
|