Class EventsOptions
- Namespace
- Fdyay.IdentityServer.Configuration
- Assembly
- Fdyay.IdentityServer.Core.dll
Which kinds of event reach the sink.
public class EventsOptions- Inheritance
-
EventsOptions
- Inherited Members
Remarks
Every flag defaults to false. Events carry client ids, subject ids and addresses, and where they
end up is the host's decision rather than this server's — so raising them is opt-in, and a host that
never configures a sink never emits anything anywhere.
The four are separate because they are wanted separately: a deployment that wants an alert on Error almost never wants a record of every successful token issuance, and one doing security monitoring wants Failure and nothing else.
Properties
IncludeStackTraceInUnhandledExceptionEvents
Put the exception's stack trace, and its inner exceptions, in UnhandledExceptionEvent.Details. Off by default.
public bool IncludeStackTraceInUnhandledExceptionEvents { get; set; }Property Value
Remarks
Off, Details carries the exception's type and message. On, it carries Exception.ToString(), which is
what Duende 8.0.1's always carries. A stack trace names this server's internals and sometimes the values it was
working on, so it is the host's decision, made knowing where its sink sends things (the decision of 2026-10-13).
Not Duende's: Duende has no switch, because it has no default without the stack.
RaiseErrorEvents
Raise events for faults in the server itself.
public bool RaiseErrorEvents { get; set; }Property Value
RaiseFailureEvents
Raise events for requests the server refused.
public bool RaiseFailureEvents { get; set; }Property Value
RaiseInformationEvents
Raise events that are neither a success nor a refusal.
public bool RaiseInformationEvents { get; set; }Property Value
RaiseSuccessEvents
Raise events for operations that succeeded.
public bool RaiseSuccessEvents { get; set; }