Logging and Monitoring
Learn how to monitor system behavior after deployment by configuring various loggings and alarms.
Logging and Monitoring Overview
A summary of the main reliability behaviors of the Curity Identity Server
The Grafana Dashboard for the Curity Identity Server
A description of the features provided by the Grafana dashboard for the Curity Identity Server
OpenTelemetry Tracing
Use OpenTelemetry tracing to help diagnose issues during distributed OAuth flows
Logging Best Practices
Recommendations for managing logs and troubleshooting the Curity Identity Server.
Add a Client IP Address to Audit Logs
Using log4j2 to store client IP address to the audit database
Debug Logging
Configure debug logging in the Curity Identity Server as part of troubleshooting.
Per-client Debug Logging in Production Environments
Using log4j2 to filter and log requests based on the calling client.
Log Aggregation to Splunk
How to configure logging to Splunk
Log Aggregation to Datadog
How to configure logging to Datadog
Log Aggregation to Elasticsearch
How to configure logging to Elasticsearch
Health and Auto Healing
How to connect to the health endpoint and use it to maintain the desired state of the Curity Identity Server
Integrate Alarms with Cloud Monitoring
Implementing a custom alarm handler to report temporary failures
Java Runtime Monitoring
Getting set up with Java Monitoring and Runtime Profiling
How to Record a Browser Trace
How to record a browser trace for troubleshooting | Curity
