In the latter case, the log output will be sent to STDOUT by default. The system log files will be placed in the logs directory under the FusionAuth installation unless you are running FusionAuth in a container. System metrics, such as JVM buffers, memory and threads.Ĭan be consumed via API and available in Prometheus compatible format. Contains IP and location information when available.Ĭan be sent to an HTTP endpoint or a Kafka topic. Triggered by events as documented, sending is configurable. This record itself is not sent through a webhook, but a login success or login failure can be consumed via a web hook. ![]() Includes IP information, application, user, and timestamp.Ĭan be consumed via API. Examples: a template rendering error in a custom theme, an exception connecting to SMTP due to bad credentials, a failure in a SAML exchange, a connection to a webhook is failing.Įach successful login is recorded here. In general, runtime errors that are typically not caused by FusionAuth and cannot be communicated well at runtime. This can be consumed via web hook or API.ĭebug information for external integrations with IdPs, SMTP etc. This is a free form API, and the audit log contents are whatever you put in. This is just an API, so a customer can also call this API. Minimal tracing capability unless debug logging is enabled.Ĭreated by the admin user interface actions. ![]() Here’s an overview table of monitoring options.Įxceptions, stack traces, database connection issues, Elasticsearch connection issues. There are a number of ways to gain this insight. Once you’ve installed FusionAuth and integrated it with your applications, you have to run it.įor that you need insight into how the system is performing. Operate / secure and monitor Monitoring FusionAuth Overview
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |