structuredlog#

Names to control how the next event identifier is generated after each event message.

Names to control what type of event identifiers will be used for each message.

Options to do a less of a strict comparison when comparing trees.

The data type contained within a JsonNode .

Possible results from registering a new schema.

The tag that is applied to structuredlog messages.

A function that registers all schemas within a module.

Free any memory allocated to a JsonNode and clear it out to an empty node.

Perform a deep comparison of two nodes.

Checks the settings registry for structured log settings and makes them active.

Retrieves a string containing the name of a SchemaResult value.

Default value for the onValidationError template parameter.

Serialize an array type from a JSON tree.

Serialize JSON using a JsonNode as the schema and a binary blob to read data.

Serialize JSON using a JsonNode as the schema and a binary blob to read data.

Serialize a scalar type from a JSON tree.

Enables or disables the structured logging log message redirection.

Base type for flags to control how new events are allocated.

Base type for the handle to an allocated block of memory returned from either the IStructuredLog::allocSchema() or IStructuredLog::allocEvent() functions.

Base type for flags to control how events and schemas are enabled or disabled.

Base type for flags to control the behavior of processing a single event.

Base type for a unique ID of a registered event.

Base type for flags that control how extra field flags are specified or retrieved in omni::structuredlog::IStructuredLogExtraFields::getExtraCloudEventField() and omni::structuredlog::IStructuredLogExtraFields::setExtraCloudEventField().

The prototype of the function to call when a validation error occurs.

The prototype of the function to call when a validation error occurs.

Base type for the ouptut flags for the structured logging system.

Base type for the version of the event payload parser to use.

Base type for the flags for that can be passed in the flags parameter to the omni::structuredlog::IStructuredLogSettings::loadPrivacySettingsFromFile() function.

Registration function to install a schema with the structured logging system.

Base type for flags to control the behavior of the handling of a schema as a whole.

Base type for a session ID.

String view for char strings.

Flag to indicate that the event should only be added to the queue on commit but that the consumer thread should not be started yet if it is not already running.

Flag to indicate that an enable state change should affect the entire system, not just one schema or event.

Flag to indicate that the enable state of each event in a schema should be overridden when the fEnableFlagWholeSchema flag is also used.

Flag to indicate that a call to IStructuredLog::setEnabled() should affect the entire schema that the named event ID belongs to instead of just the event.

Flag to indicate that this event is critical to succeed and should potentially block the calling thread on IStructuredLog::allocEvent() calls if the event queue is full.

Flag to indicate that this event should be output to the stderr file.

Flag to indicate that this event should be output to the stdout file.

Flag to indicate that this event should not be output to the schema's specified log file.

Use the log file specified by the owning event's schema instead of the default log for the process.

Value to indicate that no special flags are being specified.

Flag to indicate that the cloud heartbeat events should be emitted as well as the normal heartbeat events.

Special flag value to indicate that no output flags are being specified.

Flag to indicate that only emit the payload portion of each message as the full output instead of including the CloudEvents wrapper as well.

Flag to indicate that no header should be written out to log files created by the structured logging system.

Flag to indicate that the privacy settings keys that the privacy settings that could affect user privacy functionality should be explicitly reset to their default values before loading the new privacy file.

Flag to indicate that the log file should remain open between messages.

Flag to indicate that the log file for this schema should include the process ID in the filename.

A special value to indicate that an operation should affect all registered schemas.

The setting path that will indicate which type of anonymous user ID will be used in cases where no user ID is provided in the privacy.toml file or the privacy.toml file is missing.

A special value to indicate a bad event identifier.

The default mode for how a random user ID is chosen.

The default state for whether the cloud heartbeat events will be emitted.

The default state for whether the CloudEvents wrapper will be output with each message.

The default enable mode for the 'JSON on stdout' feature.

The default value for the event queue size in bytes.

The default minimum time between heartbeat events in seconds.

The default mode for generating event IDs.

The default type of event ID to generate.

The default log name to use.

A special name to request the log file path for the default log (if set).

A special name for the default log output path.

The default log retention setting.

Constants for default and minimum values for various settings.

The default state for whether headers will be added to each written log file.

The default high water mark for the queue.

The setting path that will indicate whether the cloud heartbeat events will be enabled.

The setting path that will indicate whether the CloudEvents wrapper should be added to the payload of each emitted event.

The setting path that indicates whether the 'JSON on stdout' functionality is enabled or not.

The setting path for the log consumer toggle.

The setting path for the event identifier mode.

The setting path for the event identifier data type.

The setting path for the size of the event queue buffer in kilobytes.

The setting path to an array that will contain zero or more values that will be used to disable or enable events when they are first registered.

The setting path that will contain zero or more keys that will be used to disable events when they are first registered.

The settings branch that will be expected to contain zero or more key/value pairs for extra fields to be added to each output message.

Names for various settings that can be used to override some of the default settings.

Special value to indicate that the heartbeat event should be disabled.

The setting path that will contain the minimum number of seconds between heartbeat events A heartbeat event is one that is sent periodically to help calculate session lengths even if the expected 'exit' or 'crash' process lifetime events are missing.

Specifies the directory that log files should be written to.

The setting path for the log retention count.

The setting path for the log size limit in megabytes.

The maximum allowed event queue size in bytes.

Approximate size of the maximum data payload in bytes that a message can contain that can be transmitted in a single message.

Approximate size of the maximum data payload in bytes that a message can contain that can be transmitted in a single message when the payload is encoded in Base64.

The minimum allowed event queue size in bytes.

The minimum allowed log retention setting.

The minimum value that can be set for the log size limit in bytes.

The setting path that will indicate whether headers will be added to each log file that is written to disk.

A special string length value to indicate that a string parameter to a generated event sending function is null terminated and should have its length calculated instead of passing in an explicit length.

The current event payload parser version that will be used in the IStructuredLog interface.

The setting path for the privacy settings file to load.

This sets the point where omni.structuredlog will decide that the queue is overfilled and will automatically increase the queue size.

The recommended size for the event queue when log redirection is enabled.

The setting path to an array that will contain zero or more values that will be used to disable or enable schemas when they are first registered.

The setting path that will contain zero or more keys that will be used to disable schemas when they are first registered.

This is the path for settings tree that contains the set of schemas or wildcards to set the maximum allowable throughput measured in bytes per second.

This is the path for settings tree that contains the set of schemas or wildcards to set the time period (in milliseconds) for the throughput limits defined by kSchemasThroughputLimitsSetting .

The expected base name for the structured log plugin.