Collecting Roving Edge Device Diagnostic Information
Use the diagnostic service to collect diagnostic information for Roving Edge devices and send them to Oracle Support where the data can be further reviewed and recommendations made on how to fix problems and improve performance.
The diagnostic service gathers logs regardless of the health of core services such as data-sync, object storage, databases, and identity. After you create and download a diagnostic bundle, submit it to Oracle Support.
You can use the diagnostic service in the following modes:
Normal Mode
Use this mode when all Roving Edge services start and run as usual. The calling diagnostic API is authenticated through the on-device Identity service. This mode requires no special preparation of the device.
The following table lists the tasks you perform in this mode.
| No. | Task | Description |
|---|---|---|
| 1. | Create a Diagnostic Bundle | You can create the bundle using the Device Console or the CLI. |
| 2. | Download the Diagnostic Bundle | Use the Device Console to download a diagnostic bundle to your computer. |
| 3. | Decrypt and submit the diagnostics bundle |
Decrypt the bundle on your computer. Then open an Oracle Support Request and upload the decrypted diagnostic bundle as part of your support request ticket. |
Standard Mode
Use this mode when all Roving Edge services run as usual. This mode differs from normal mode in the following ways:
-
The calling diagnostic API is authenticated using basic user authentication instead of the local on-device Identity service. Basic user authentication is a temporary user and password that's issued to you when you put the device into standard mode. These credentials are required to submit the diagnostic bundle.
-
You must use the CLI to create the diagnostic bundle. You can't use the Device Console.
The following table lists the tasks you perform in this mode.
| No. | Task | Description |
|---|---|---|
| 1. | Enabling Diagnostics Standard Mode | Use the Serial Console to put the device in standard mode. |
| 2. | Create a Diagnostic Bundle | You create the bundle using the CLI. |
| 3. | Download the Diagnostic Bundle | Use the Device Console to download a diagnostic bundle to your computer. |
| 4. | Decrypt and submit the diagnostics bundle |
Decrypt the bundle on your computer. Then open an Oracle Support Request and upload the decrypted diagnostic bundle as part of your support request ticket. |
| 5. | Exit from the diagnostics mode. | Exit the diagnostics mode. |
Minimum Services Mode
Use this mode when the device isn't running services as usual.
You use the Serial Console menu to put the device into Minimum data collection mode which results in rebooting the device with the minimum set of services. Basic user authentication is used in this mode (See Standard Mode for a description of basic user authentication).
The following table lists the tasks you perform in this mode
| No. | Task | Description |
|---|---|---|
| 1. | Enabling Diagnostics Minimum Services Mode | Use the Serial Console to put the device in standard mode. |
| 2. | Create a Diagnostic Bundle | You create the bundle using the CLI. |
| 3. | Download the Diagnostic Bundle | Use the Device Console to download a diagnostic bundle to your computer. |
| 4. | Decrypt and submit the diagnostics bundle |
Decrypt the bundle on your computer. Then open an Oracle Support Request and upload the decrypted diagnostic bundle as part of your support request ticket. |
| 5. | Exit from the diagnostics mode. | Exit the diagnostics mode. A reboot is required. |