> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/es/administracion-del-sistema/sel.md).

# El registro de eventos del sistema (SEL)

Cómo ver y borrar el Registro de eventos del sistema IPMI (SEL) en nodos VergeOS, incluida la supervisión de capacidad y la gestión del registro.

El Registro de eventos del sistema (SEL) contiene eventos de la interfaz IPMI del hardware. Dado que este registro se almacena en el hardware, su capacidad es limitada; cuando el SEL se llena, no se pueden registrar nuevos eventos hasta que se borre. El panel del nodo muestra una barra de porcentaje para indicar la cantidad de capacidad del SEL que se está utilizando actualmente en el nodo.

## Borrar el SEL de un nodo

1. En el menú superior, vaya a **Infraestructura** > **Nodos**.
2. **Haga doble clic en el nodo deseado** para acceder al **panel del nodo**.
3. Haga clic en **Borrar SEL** en el menú de la izquierda.
4. Haga clic en **Sí** para confirmar.


---

# 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.verge.io/run-the-platform/es/administracion-del-sistema/sel.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.