> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/es/comandos-de-powershell/write-psulog.md).

# Write-PSULog

## SINOPSIS

Escribe un registro en el sistema de registro de PowerShell Universal.

## SINTAXIS

```
Write-PSULog [-Message] <String> [-Feature <String>] [-Resource <String>] [-Level <AgentLogLevel>]
 [-Properties <Hashtable>] [-Console] [<CommonParameters>]
```

## DESCRIPCIÓN

Escribe un registro en el sistema de registro de PowerShell Universal.

## EJEMPLOS

### Ejemplo 1

```powershell
PS C:\> Write-PSULog -Message "Hello" -Level 'Error'
```

Escribe un registro de error en el sistema de registro de PowerShell Universal.

## PARÁMETROS

### -Feature

La función que escribe el registro. Normalmente es el nombre del grupo de funciones. Por ejemplo, 'App' o 'API'.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Level

El nivel del registro. Puede ser Error, Warning, Information o Debug.

```yaml
Type: AgentLogLevel
Parameter Sets: (All)
Aliases:
Accepted values: Error, Warning, Information, Debug

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Message

El mensaje que se escribirá en el registro.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: True
Position: 0
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Properties

Propiedades adicionales que se escribirán en el registro. Debe ser una tabla hash de pares clave/valor.

```yaml
Type: Hashtable
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Resource

El recurso al que se asociará este mensaje de registro. Puede ser una app, una API o un script.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Console

También escribe la entrada de registro en la salida de la consola.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable y -ProgressAction. Para obtener más información, consulte [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## ENTRADAS

### Ninguna

## SALIDAS

### System.Object

## NOTAS

## ENLACES RELACIONADOS


---

# 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.devolutions.net/powershell-universal/es/comandos-de-powershell/write-psulog.md?ask=<question>&goal=<endgoal>
```

`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.