medcrypt::guardian::InitializeOptions

Overview

These are the initialization configuration options to initialize Guardian.

Include:

#include <InitializeOptions.h>

Syntax:

struct medcrypt::guardian::InitializeOptions;

Structure members

• is_mocked: Mocked profile flag

• log_level: Log level enumeration

Member details

is_mocked:

• Description: Mocked profile flag that determines whether the profile provided for initialization is a non-node locked 'mocked' testing profile.

• Type: bool

• Default value: false

• Syntax:

bool is_mocked = false;

log_level:

• Description: Log level enumeration. See LogLevelEnum.h for accepted levels.

• Type: LogLevelEnum::Type

• Default value: LogLevelEnum::Warn

• Syntax:

LogLevelEnum::Type log_level = [LogLevelEnum::Warn](/Namespaces/namespacemedcrypt-guardian-LogLevelEnum.md#enumvalue-warn);

Related classes

• Guardian class: Uses InitializeFiles in Initialize() function

• LogLevelEnum namespace: Contains log level values

Debugging and logging

Guardian does not create log files. Instead, logging is controlled by the application:

• Guardian logs to stdout and stderr, which appear in the terminal/CLI of the running application during execution. Look for specific error codes or connection failures in the output.

• Custom logging: Use SetLoggingCallback to redirect log messages to a callback function, stopping terminal output and allowing custom log handling

• Log control: Applications can control log level and verbosity.

• Guardian Cloud UI: Check the Guardian Cloud interface for additional error details and provisioning status.