medcrypt::guardian::ProvisioningOptions

Options used by Guardian::StartProvisioningOnlinearrow-up-right.

#include <GuardianProvisioningOptions.h>

Public Functions

Public Attributes

Name

std::chrono::system_clock::duration

connection_timeoutarrow-up-right Initial connection timeout.

std::chrono::system_clock::duration

response_timeoutarrow-up-right Time to wait for server response.

std::chrono::system_clock::duration

packet_resendarrow-up-right Server polling time.

Public Functions Documentation

function ~ProvisioningOptions

~ProvisioningOptions()

Public Attributes Documentation

variable connection_timeout

Initial connection timeout.

If the connection does not complete within connection_timeout the online provisioning process will fail.

variable response_timeout

Time to wait for server response.

If the server does not respond with any status within response_timeout the online provisioning process will fail.

variable packet_resend

Server polling time.

Once the server has responded with any non-failing status, do not send another polling request until packet_resend has elapsed since the last request was sent.

Example: if packet_resend is 10 seconds, and the server response occurs 5 seconds after the initial request was sent, the next request will be sent approximately 5 seconds later.

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.

Last updated