> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/guardian/api-overview/api-reference/classes/structmedcrypt-guardian-provisioningoptions.md).

# medcrypt::guardian::ProvisioningOptions

Options used by [Guardian::StartProvisioningOnline](/medcrypt-documentation/guardian/api-overview/api-reference/classes/classmedcrypt-guardian-guardian.md#function-startprovisioningonline).

`#include <GuardianProvisioningOptions.h>`

## Public Functions

|   | Name                                                          |
| - | ------------------------------------------------------------- |
|   | [**\~ProvisioningOptions**](#function-~provisioningoptions)() |

## Public Attributes

|                                      | Name                                                                                                                    |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| std::chrono::system\_clock::duration | <p><a href="#variable-connection_timeout"><strong>connection\_timeout</strong></a><br>Initial connection timeout.</p>   |
| std::chrono::system\_clock::duration | <p><a href="#variable-response_timeout"><strong>response\_timeout</strong></a><br>Time to wait for server response.</p> |
| std::chrono::system\_clock::duration | <p><a href="#variable-packet_resend"><strong>packet\_resend</strong></a><br>Server polling time.</p>                    |

## Public Functions Documentation

### function \~ProvisioningOptions

```cpp
~ProvisioningOptions()
```

## Public Attributes Documentation

### variable connection\_timeout

```cpp
std::chrono::system_clock::duration connection_timeout = std::chrono::seconds(10);
```

Initial connection timeout.

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

### variable response\_timeout

```cpp
std::chrono::system_clock::duration response_timeout = std::chrono::seconds(10);
```

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

```cpp
std::chrono::system_clock::duration packet_resend = std::chrono::seconds(10);
```

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.medcrypt.com/medcrypt-documentation/guardian/api-overview/api-reference/classes/structmedcrypt-guardian-provisioningoptions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.