Transaction Log
The Transaction Log configuration category includes the following configurable options:
Transaction Log Broker Channel Name
Event Blacklist
Event Whitelist
Persist Transaction Bodies (All)
Persist Transaction Bodies: Incoming Request
Persist Transaction Bodies: Incoming Response
Persist Storage Outcome Details
Transaction Log Step Body Serialization Mode
Transaction Log Broker Enabled (DEPRECATED)
Cluster Manager Transaction Log Storage
Transaction Log Show Request Body Enabled
Truncate Transaction Bodies (bytes)
|
Transaction Log Broker Channel Name |
|
|
STRING | |
The transaction logs will be sent to the specified topic/queue name. Must be non-empty. | |
|
|
smilecdr-transaction
|
|
|
|
Event Blacklist |
|
|
STRING | |
This setting provides a blacklist of event Type/SubType codes that should not be stored in the Transaction Log. See Controlling Transaction Log Events for more information. | |
|
|
(no default) | |
|
|
Event Whitelist |
|
|
STRING | |
This setting provides a whitelist of event Type/SubType codes to be stored in the Transaction Log. See Controlling Transaction Log Events for more information. | |
|
|
(no default) | |
|
|
Persist Transaction Bodies (All) |
|
|
BOOLEAN | |
If enabled, the payload bodies of transactions will be persisted in the transaction log. This can be useful for troubleshooting; however, it has database capacity and performance implications under heavy load. This configuration is enabled by default. Note that this is a primary switch, and disabling it takes precedence over any more specific persistence switches. Also note that for historical reasons, this setting includes the word "clustermgr" in its name, but it does not only apply to the Cluster Manager. If this setting is applied to the Cluster Manager module, it controls whether payload bodies are stored in transaction log entries in the cluster manager database. If it is applied to a Transaction Log Persistence module, it controls whether payload bodies are stored in that module's database, etc. | |
|
|
true
|
|
|
|
Persist Transaction Bodies: Incoming Request |
|
|
BOOLEAN | |
If enabled, incoming request transaction bodies (e.g. the request body for a FHIR create request received by a FHIR Endpoint module) will be persisted in the transaction log. | |
|
|
true
|
|
|
|
Persist Transaction Bodies: Incoming Response |
|
|
BOOLEAN | |
If enabled, incoming response transaction bodies (e.g. the response body for a FHIR search request received by a FHIR Endpoint module) will be persisted in the transaction log. | |
|
|
true
|
|
|
|
Persist Storage Outcome Details |
|
|
BOOLEAN | |
Enabled storage of individual Storage Outcome Details within the generated Transaction Log entries when processing FHIR Transaction or Batch operations. | |
|
|
false
|
|
|
|
Transaction Log Step Body Serialization Mode |
|
|
ENUM | |
Values |
|
Controls whether the transaction log step body is serialized as formatted JSON or flattened(inline) | |
|
|
FHIR_JSON
|
|
|
|
Transaction Log Broker Enabled (DEPRECATED) |
|
|
BOOLEAN | |
If enabled, the transaction log will submit events to the configured broker for use in realtime reporting. This setting is deprecated; this functionality is available using the Transaction Log Broker Module. | |
|
|
false
|
|
|
|
Cluster Manager Transaction Log Storage |
|
|
BOOLEAN | |
This setting enables storage of Transaction Log events directly in the Cluster Manager database. This should be disabled unless you specifically want to store your transaction log events directly in the Cluster Manager database. | |
|
|
true
|
|
|
|
Transaction Log Show Request Body Enabled |
|
|
BOOLEAN | |
If enabled, the transaction log will show the body of the FHIR request events. | |
|
|
false
|
|
|
|
Truncate Transaction Bodies (bytes) |
|
|
NON_NEGATIVE_INTEGER | |
If set to a positive integer, transaction log payload bodies will be truncated before being stored in the transaction log. | |
|
|
10000
|
|
|
You are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.