> 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/de/powershell-befehle/write-psulog.md). # Write-PSULog Write-PSULog schreibt eine Nachricht mit einem Schweregrad, einer Funktion und einem Ressourcen-Tag in das Protokollierungssystem von PowerShell Universal. ## SYNOPSIS Schreibt ein Protokoll in das Protokollierungssystem von PowerShell Universal. ## SYNTAX ``` Write-PSULog [-Message] [-Feature ] [-Resource ] [-Level ] [-Properties ] [-Console] [] ``` ## BESCHREIBUNG Schreibt ein Protokoll in das Protokollierungssystem von PowerShell Universal. ## BEISPIELE ### Beispiel 1 ```powershell PS C:\> Write-PSULog -Message "Hello" -Level 'Error' ``` Schreibt ein Fehlerprotokoll in das Protokollierungssystem von PowerShell Universal. ## PARAMETER ### -Feature Die Funktion, die das Protokoll schreibt. Dies ist normalerweise der Name der Funktionsgruppe. Zum Beispiel 'App' oder 'API'. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Level Die Ebene des Protokolls. Dies kann Error, Warning, Information oder Debug sein. ```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 Die Nachricht, die in das Protokoll geschrieben wird. ```yaml Type: String Parameter Sets: (All) Aliases: Required: True Position: 0 Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Properties Zusätzliche Eigenschaften, die in das Protokoll geschrieben werden. Dies sollte eine Hashtabelle mit Schlüssel-Wert-Paaren sein. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Resource Die Ressource, mit der diese Protokollnachricht verknüpft wird. Dies kann eine App, eine API oder ein Skript sein. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Console Schreibt den Protokolleintrag außerdem in die Konsolenausgabe. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Dieses Cmdlet unterstützt die allgemeinen Parameter: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable und -ProgressAction. Weitere Informationen finden Sie unter [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## EINGABEN ### Keine ## AUSGABEN ### System.Object ## HINWEISE ## VERWANDTE LINKS --- # 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/de/powershell-befehle/write-psulog.md?ask=&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.