GET Config Data
Export LogInsight configuration into a file, which can be used for configuring a fresh Operations for Logs setup.
Exported configuration includes the following information about the LogInsight cluster:
- General configuration (CEIP, System notification recipients, etc.)
- NTP configuration
- Log forwarder configuration
- SMTP configuration
- Archiving settings
- Agents groups configuration
Exported configuration does NOT include the following information:
- Cluster configuration (e.g. the number of nodes, VIP configuration, etc.) Exporting VIP configuration might result in multiple clusters having the same VIP, which would cause issues with ingestion, log forwarding, etc.
- Hosts information
- Patterns and fields extracted during machine learning
- Agents configuration
- Local users. Local users aren't migrated for security reasons so that passwords are exposed in the exported configuration file.
- Active Directory and vIDM configurations aren't migrated for security reasons, as exporting these configurations would expose the passwords.
- Content packs and user content, such as dashboards, alerts, etc.
- SSL configuration
- vSphere integration configuration isn't migrated for security reasons, as exporting this configuration would expose the passwords.
- VMware Aria Operations integration configuration isn't migrated for security reasons, as exporting this configuration would expose the passwords.
Response Headers
Additional information about the life-cycle status of the API.
Indicates the life-cycle status of the API.
The request was refused because it lacks valid authentication
credentials. This can happen if the Authorization header
was missing, or if it contained an invalid session ID.
Obtain a new session ID and retry the request,
or make an unauthenticated request without the Authorization header.
"Invalid session ID"
The request was refused because the session ID has
expired. Obtain a new session ID from /api/v1/sessions.
"Login Timeout"
Internal error while processing the client request
{
"errorMessage": "The operation failed due to an internal error."
}
A message describing the error.
A code representing the type of error.
Dynamic error details, where the field name can vary depending on the request field and error code.
curl -H 'Authorization: <value>' https://{api_host}/api/v1/config/data