# Logs

The **Logs** section provides access to the **instance console logs**, which contain system boot and runtime messages.

These logs help users diagnose instance startup issues, operating system errors, and system-level events.

Console logs are especially useful for troubleshooting when remote access (SSH or RDP) is unavailable.

### Access Console Logs

To view instance logs:

1. Log in to the **NeevCloud Dashboard**.
2. Navigate to **CLOUD→ Servers**.
3. Select the required **Cloud Instance**.
4. Click **Logs** from the left-side menu.

The system will display the **Instance Console Logs**.

<figure><img src="https://1876135298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEC5NwtFshv6EATOemuUn%2Fuploads%2FfJ2btE2ovnaJZ8wOIqJv%2Fimage.png?alt=media&#x26;token=38f80ed8-adfe-429d-a3e8-0b31afae72f4" alt=""><figcaption></figcaption></figure>

***

### What Console Logs Contain

Console logs may include:

* Operating system boot messages
* Kernel initialisation logs
* Service startup messagesinitialisation
* System errors or warnings
* Application initialisation output

These logs help determine whether the instance boot process completed successfully.

***

### Common Use Cases

Console logs can help diagnose:

* Instance boot failures
* Kernel or OS errors
* Misconfigured services
* Application startup problems
* Initialisation script failures

***

### Important Notes

* Console logs are **read-only** and intended for troubleshooting.
* The logs reflect **system-level messages generated during boot and runtime**.
* Logs may rotate depending on the operating system configuration.

{% hint style="info" %}
💡 Tip

If your instance becomes inaccessible via SSH or RDP, the **Logs** section can help identify boot or configuration issues directly from the console output.
{% endhint %}