> 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/it/comandi-powershell/write-psulog.md).

# Write-PSULog

Write-PSULog scrive un messaggio con un livello di gravità, una funzionalità e un tag di risorsa nel sistema di logging di PowerShell Universal.

## SINOSSI

Scrive un log nel sistema di logging di PowerShell Universal.

## SINTASSI

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

## DESCRIZIONE

Scrive un log nel sistema di logging di PowerShell Universal.

## ESEMPI

### Esempio 1

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

Scrive un log di errore nel sistema di logging di PowerShell Universal.

## PARAMETRI

### -Feature

La funzionalità che scrive il log. In genere è il nome del gruppo di funzionalità. Ad esempio, '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

Il livello del log. Può essere 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

Il messaggio da scrivere nel log.

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

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

### -Properties

Proprietà aggiuntive da scrivere nel log. Deve essere una hashtable di coppie chiave/valore.

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

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

### -Resource

La risorsa a cui associare questo messaggio di log. Può essere un'app, un'API o uno script.

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

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

### -Console

Scrive la voce di log anche nell'output della console.

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

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

### CommonParameters

Questo cmdlet supporta i parametri comuni: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable e -ProgressAction. Per maggiori informazioni, veda [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUT

### Nessuno

## OUTPUT

### System.Object

## NOTE

## COLLEGAMENTI CORRELATI


---

# 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.devolutions.net/powershell-universal/it/comandi-powershell/write-psulog.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.