> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-products/computes/manage-cloud-instance/logs.md).
# 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**.
***
### 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 %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.neevcloud.com/neevcloud-products/computes/manage-cloud-instance/logs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.