- API >
- Public API Resources >
- Log Collection Jobs >
- Retry a Failed Log Collection Job
Retry a Failed Log Collection Job¶
On this page
Note
Groups and projects are synonymous terms. Your {PROJECT-ID}
is the
same as your project id. For existing groups, your group/project id
remains the same. This page uses the more familiar term group when
referring to descriptions. The endpoint remains as stated in the
document.
When you create a log collection job, Ops Manager starts a background job to download the logs from the specified Ops Manager deployment. Use this endpoint to retry a single failed log collection job.
To check if a log collection job failed, you can use the
Get All Log Collection Jobs for One Project and Get a Single Log Collection Job endpoints. The
status
response element shows FAILURE
for failed log collection
jobs.
Base URL: https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0
Resource¶
Request Path Parameters¶
Name | Type | Description |
---|---|---|
PROJECT-ID |
string | Unique identifier of the project that the log collection job is associated with. |
JOB-ID |
string | Unique identifier of the log collection job to retry.
You can obtain the JOB-IDs associated with your project by
using the
Get All Log Collection Jobs for One Project
endpoint. |
Request Query Parameters¶
The following query parameters are optional:
Name | Type | Description | Default | ||||||
---|---|---|---|---|---|---|---|---|---|
pretty |
boolean | Flag indicating whether the response body should be in a prettyprint format. | false |
||||||
envelope |
boolean | Flag indicating whether or not to wrap the response in an envelope. Some API clients cannot access the HTTP response headers or
status code. To remediate this, set For endpoints that return one result, the response body includes:
|
false |
Request Body Parameters¶
This endpoint does not use HTTP request body parameters.
Response¶
This endpoint does not have response elements.