public class JsonStdoutAuditEventHandler extends AuditEventHandlerBase
AuditEventHandler for persisting raw JSON events to a file.
The file format is a UTF-8 text-file, with one JSON event per line, and each line terminated by a newline character.
eventTopicsMetaData| Constructor and Description |
|---|
JsonStdoutAuditEventHandler(JsonStdoutAuditEventHandlerConfiguration configuration,
EventTopicsMetaData eventTopicsMetaData)
Creates a
JsonAuditEventHandler instances. |
| Modifier and Type | Method and Description |
|---|---|
Promise<ResourceResponse,ResourceException> |
publishEvent(Context context,
String topic,
JsonValue event)
Publishes an event to the provided topic.
|
Promise<QueryResponse,ResourceException> |
queryEvents(Context context,
String topic,
QueryRequest queryRequest,
QueryResourceHandler handler)
Query some events from the provided topic.
|
Promise<ResourceResponse,ResourceException> |
readEvent(Context context,
String topic,
String resourceId)
Reads an event with the provided resource id from the provided topic.
|
void |
shutdown()
Instruct this object to flush any buffers and close any open file handles or network connections.
|
void |
startup()
Instruct this object that it is safe to initialize file handles and network connections.
|
getHandledTopics, getName, handleAction, isEnabledpublic JsonStdoutAuditEventHandler(JsonStdoutAuditEventHandlerConfiguration configuration, EventTopicsMetaData eventTopicsMetaData)
JsonAuditEventHandler instances.configuration - ConfigurationeventTopicsMetaData - Provides meta-data describing the audit event topics this handler may have to handle.public void startup()
AuditEventHandlerAuditService and its handlers is achieved by replacing
rather than modifying the existing objects. Therefore, it's essential that the replacements do not perform
any I/O that would interfere with the operation of the objects they are replacing until the old objects are
shutdown. For example, when shutting down an old instance of a file-based AuditEventHandler, the old instance
may need to flush buffers, apply file rotation or retention policies, or even add line or block signatures
as part of tamper evident logging. Any of these operations could be broken if two handler instances are
operating on the same set of files simultaneously.public void shutdown()
AuditEventHandlerpublic Promise<ResourceResponse,ResourceException> publishEvent(Context context, String topic, JsonValue event)
AuditEventHandlercontext - The context chain that initiated the event.topic - The topic where to publish the event.event - The event to publish.public Promise<ResourceResponse,ResourceException> readEvent(Context context, String topic, String resourceId)
AuditEventHandlercontext - The context chain that initiated the event.topic - The topic where event is read.resourceId - The identifier of the event.public Promise<QueryResponse,ResourceException> queryEvents(Context context, String topic, QueryRequest queryRequest, QueryResourceHandler handler)
AuditEventHandlercontext - The context chain that initiated the event.topic - The topic on which query is performed.queryRequest - The request with the query.handler - The handler to process responses for the query.Copyright © 2025 Open Identity Platform Community. All rights reserved.