Get-PveNodesTasksLog
Read task log.
API: GET /nodes/{node}/tasks/{upid}/log, Proxmox VE API viewer
Syntax
Section titled “Syntax”Get-PveNodesTasksLog [-PveTicket <PveTicket>] [-Download <bool>] [-Limit <int>] -Node <string> [-Start <int>] -Upid <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Download |
bool |
No | Whether the tasklog file should be downloaded. This parameter can’t be used in conjunction with other parameters. |
-Limit |
int |
No | The number of lines to read from the tasklog. |
-Node |
string |
Yes | The cluster node name. |
-Start |
int |
No | Start at this line when reading the tasklog. |
-Upid |
string |
Yes | The task’s unique ID. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
