openapi: 3.0.0
info:
title: Sumo Logic accessKeyManagement parsersLibraryManagement API
description: "# Getting Started\nWelcome to the Sumo Logic API reference. You can use these APIs to interact with the Sumo Logic platform. For information on Collector and Search Job APIs, see our [API home page](https://help.sumologic.com/docs/api).\n## API Endpoints\nSumo Logic has several deployments in different geographic locations. You'll need to use the Sumo Logic API endpoint corresponding to your geographic location. See the table below for the different API endpoints by deployment. For details determining your account's deployment, see [API endpoints](https://help.sumologic.com/?cid=3011).\n\n
\n \n | Deployment | \n Endpoint | \n
\n \n | AU | \n https://api.au.sumologic.com/api/ | \n
\n \n | CA | \n https://api.ca.sumologic.com/api/ | \n
\n \n | DE | \n https://api.de.sumologic.com/api/ | \n
\n \n | EU | \n https://api.eu.sumologic.com/api/ | \n
\n \n | FED | \n https://api.fed.sumologic.com/api/ | \n
\n \n | IN | \n https://api.in.sumologic.com/api/ | \n
\n \n | JP | \n https://api.jp.sumologic.com/api/ | \n
\n \n | KR | \n https://api.kr.sumologic.com/api/ | \n
\n \n | US1 | \n https://api.sumologic.com/api/ | \n
\n \n | US2 | \n https://api.us2.sumologic.com/api/ | \n
\n
\n\n## Authentication\nSumo Logic supports the following options for API authentication:\n- Access ID and Access Key\n- Base64 encoded Access ID and Access Key\n\nSee [Access Keys](https://help.sumologic.com/docs/manage/security/access-keys) to generate an Access Key. Make sure to copy the key you create, because it is displayed only once.\nWhen you have an Access ID and Access Key you can execute requests such as the following:\n ```bash\n curl -u \":\" -X GET https://api..sumologic.com/api/v1/users\n ```\n\nWhere `deployment` is either `au`, `ca`, `de`, `eu`, `fed`, `in`, `jp`, `us1`, or `us2`. See [API endpoints](#section/API-Endpoints) for details.\n\nIf you prefer to use basic access authentication, you can do a Base64 encoding of your `:` to authenticate your HTTPS request. The following is an example request, replace the placeholder `` with your encoded Access ID and Access Key string:\n ```bash\n curl -H \"Authorization: Basic \" -X GET https://api..sumologic.com/api/v1/users\n ```\n\n\nRefer to [API Authentication](https://help.sumologic.com/?cid=3012) for a Base64 example.\n\n## Status Codes\nGeneric status codes that apply to all our APIs. See the [HTTP status code registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) for reference.\n \n \n | HTTP Status Code | \n Error Code | \n Description | \n
\n \n | 301 | \n moved | \n The requested resource SHOULD be accessed through returned URI in Location Header. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---301-error---moved) for details. | \n
\n \n | 401 | \n unauthorized | \n Credential could not be verified. | \n
\n \n | 403 | \n forbidden | \n This operation is not allowed for your account type or the user doesn't have the role capability to perform this action. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---401-error---credential-could-not-be-verified) for details. | \n
\n \n | 404 | \n notfound | \n Requested resource could not be found. | \n
\n \n | 405 | \n method.unsupported | \n Unsupported method for URL. | \n
\n \n | 415 | \n contenttype.invalid | \n Invalid content type. | \n
\n \n | 429 | \n rate.limit.exceeded | \n The API request rate is higher than 4 request per second or inflight API requests are higher than 10 request per second. | \n
\n \n | 500 | \n internal.error | \n Internal server error. | \n
\n \n | 503 | \n service.unavailable | \n Service is currently unavailable. | \n
\n
\n\n## Filtering\nSome API endpoints support filtering results on a specified set of fields. Each endpoint that supports filtering will list the fields that can be filtered. Multiple fields can be combined by using an ampersand `&` character.\n\nExample: To get user with email `john@demo.com`:\n ```bash\n api.sumologic.com/v1/users?email=john@demo.com\n ```\n\n## Sorting\nSome API endpoints support sorting fields by using the `sortBy` query parameter. The default sort order is ascending. Prefix the field with a minus sign `-` to sort in descending order.\n\nFor example, to get 20 users sorted by their `email` in descending order:\n ```bash\n api.sumologic.com/v1/users?limit=20&sort=-email\n ```\n\n## Asynchronous Request\nAsynchronous requests do not wait for results, instead they immediately respond back with a job identifier while the job runs in the background. You can use the job identifier to track the status of the asynchronous job request. Here is a typical flow for an asynchronous request.\n1. Start an asynchronous job. On success, a job identifier is returned. The job identifier uniquely identifies\n your asynchronous job.\n\n2. Once started, use the job identifier from step 1 to track the status of your asynchronous job. An asynchronous\n request will typically provide an endpoint to poll for the status of asynchronous job. A successful response\n from the status endpoint will have the following structure:\n ```json\n {\n \"status\": \"Status of asynchronous request\",\n \"statusMessage\": \"Optional message with additional information in case request succeeds\",\n \"error\": \"Error object in case request fails\"\n }\n ```\n The `status` field can have one of the following values:\n 1. `Success`: The job succeeded. The `statusMessage` field might have additional information.\n 2. `InProgress`: The job is still running.\n 3. `Failed`: The job failed. The `error` field in the response will have more information about the failure.\n\n3. Some asynchronous APIs may provide a third endpoint (like [export result](#operation/getAsyncExportResult))\n to fetch the result of an asynchronous job.\n\n\n### Example\nLet's say we want to export a folder with the identifier `0000000006A2E86F`. We will use the [async export](#operation/beginAsyncExport) API to export all the content under the folder with `id=0000000006A2E86F`.\n1. Start an export job for the folder\n ```bash\n curl -X POST -u \":\" https://api..sumologic.com/api/v2/content/0000000006A2E86F/export\n ```\n See [authentication section](#section/Authentication) for more details about `accessId`, `accessKey`, and\n `deployment`.\n On success, you will get back a job identifier. In the response below, `C03E086C137F38B4` is the job identifier.\n ```bash\n {\n \"id\": \"C03E086C137F38B4\"\n }\n ```\n\n2. Now poll for the status of the asynchronous job with the [status](#operation/getAsyncExportStatus) endpoint.\n ```bash\n curl -X GET -u \":\" https://api..sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/status\n ```\n You may get a response like\n ```json\n {\n \"status\": \"InProgress\",\n \"statusMessage\": null,\n \"error\": null\n }\n ```\n It implies the job is still in progress. Keep polling till the status is either `Success` or `Failed`.\n\n3. When the asynchronous job completes (`status != \"InProgress\"`), you can fetch the results with the\n [export result](#operation/getAsyncExportResult) endpoint.\n ```bash\n curl -X GET -u \":\" https://api..sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/result\n ```\n\n The asynchronous job may fail (`status == \"Failed\"`). You can look at the `error` field for more details.\n ```json\n {\n \"status\": \"Failed\",\n \"errors\": {\n \"code\": \"content1:too_many_items\",\n \"message\": \"Too many objects: object count(1100) was greater than limit 1000\"\n }\n }\n ```\n\n\n## Rate Limiting\n* A rate limit of four API requests per second (240 requests per minute) applies to all API calls from a user.\n* A rate limit of 10 concurrent requests to any API endpoint applies to an access key.\n\nIf a rate is exceeded, a rate limit exceeded 429 status code is returned.\n\n## Generating Clients\nYou can use [OpenAPI Generator](https://openapi-generator.tech) to generate clients from the YAML file to access the API.\n\n### Using [NPM](https://www.npmjs.com/get-npm)\n1. Install [NPM package wrapper](https://github.com/openapitools/openapi-generator-cli) globally, exposing the CLI\n on the command line:\n ```bash\n npm install @openapitools/openapi-generator-cli -g\n ```\n You can see detailed instructions [here](https://openapi-generator.tech/docs/installation#npm).\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n\n\n### Using [Homebrew](https://brew.sh/)\n1. Install OpenAPI Generator\n ```bash\n brew install openapi-generator\n ```\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client side code inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n"
version: 1.0.0
x-logo:
url: ./sumologic_logo.png
servers:
- url: https://api.au.sumologic.com/api/
description: AU deployment API server
- url: https://api.ca.sumologic.com/api/
description: CA deployment API server
- url: https://api.de.sumologic.com/api/
description: DE deployment API server
- url: https://api.eu.sumologic.com/api/
description: EU deployment API server
- url: https://api.fed.sumologic.com/api/
description: FED deployment API server
- url: https://api.jp.sumologic.com/api/
description: JP deployment API server
- url: https://api.kr.sumologic.com/api/
description: KR deployment API server
- url: https://api.in.sumologic.com/api/
description: IN deployment API server
- url: https://api.sumologic.com/api/
description: US1 deployment API server
- url: https://api.us2.sumologic.com/api/
description: US2 deployment API server
security:
- basicAuth: []
tags:
- name: parsersLibraryManagement
description: 'Parsers Library Management API
Customize the Parsers via this API. The Parsers Library contains the Parsers used in the "_parser" field for collector, FER or query. For more information on customizing parsers, see [Parser Editor](https://help.sumologic.com/docs/cse/schema/parser-editor/).
'
x-displayName: Parsers Library Management
paths:
/v1/parsers/root:
get:
tags:
- parsersLibraryManagement
summary: Get The Root Folder In The Library.
description: 'Get the root folder in the library.
'
operationId: getParsersLibraryRoot
responses:
'200':
description: Root folder in the library.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryFolderResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers:
get:
tags:
- parsersLibraryManagement
summary: Bulk Read Folders And Parsers.
description: 'Bulk read folders and parsers by the given identifiers from the library.
'
operationId: parsersReadByIds
parameters:
- name: ids
in: query
description: A comma-separated list of identifiers.
required: true
schema:
type: array
example: 0000000000000001,0000000000000002,0000000000000003
items:
type: string
responses:
'200':
description: A map between an identifier and its definition (folder or parser).
content:
application/json:
schema:
$ref: '#/components/schemas/IdToParsersLibraryBaseResponseMap'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- parsersLibraryManagement
summary: Create A Folder Or Parser.
description: 'Create a folder or parser.
'
operationId: parsersCreate
parameters:
- name: parentId
in: query
description: Identifier of the parent folder in which to create the folder or parser.
required: true
schema:
type: string
requestBody:
description: The folder or parser to be created.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBase'
required: true
responses:
'200':
description: Newly created folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- parsersLibraryManagement
summary: Bulk Delete Folders And Parsers.
description: 'Bulk delete folders and parsers by the given identifiers from the library.
'
operationId: parsersDeleteByIds
parameters:
- name: ids
in: query
description: A comma-separated list of identifiers.
required: true
schema:
type: array
example: 0000000000000001,0000000000000002,0000000000000003
items:
type: string
responses:
'200':
description: A map between the deleted identifier and its meta data.
content:
application/json:
schema:
$ref: '#/components/schemas/IdToParsersLibraryBaseResponseMap'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}:
get:
tags:
- parsersLibraryManagement
summary: Read A Folder Or Parser.
description: 'Read a folder or parser.
'
operationId: parsersReadById
parameters:
- name: id
in: path
description: Identifier of the folder or parser to read.
required: true
schema:
type: string
responses:
'200':
description: Requested folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- parsersLibraryManagement
summary: Update A Folder Or Parser.
description: 'Update a folder or parser.
'
operationId: parsersUpdateById
parameters:
- name: id
in: path
description: Identifier of the folder or parser to update.
required: true
schema:
type: string
requestBody:
description: 'The folder or parser to be updated. Content version must match its latest version number in the library. Any staled version will not be updated.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseUpdate'
required: true
responses:
'200':
description: Updated folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- parsersLibraryManagement
summary: Delete A Folder Or Parser.
description: 'Delete a folder or parser.
'
operationId: parsersDeleteById
parameters:
- name: id
in: path
description: Identifier of the folder or parser to delete.
required: true
schema:
type: string
responses:
'204':
description: The folder or parser was successfully deleted.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/path:
get:
tags:
- parsersLibraryManagement
summary: Get Full Path Of Folder Or Parser.
description: 'Get full path of folder or parser.
'
operationId: getParsersFullPath
parameters:
- name: id
in: path
description: Identifier of the folder or parser.
required: true
schema:
type: string
responses:
'200':
description: Full path of the folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/Path'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/lock:
post:
tags:
- parsersLibraryManagement
summary: Lock A Folder Or A Parser.
description: 'Locking requires the `LockParsers` capability. When an object is locked, it can''t be moved or deleted and only the local fields can be modified. Locking recursively locks all of the objects children.
'
operationId: parsersLockById
parameters:
- name: id
in: path
description: The id of the folder or parser that needs to be locked.
required: true
schema:
type: string
responses:
'200':
description: Updated folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/unlock:
post:
tags:
- parsersLibraryManagement
summary: Unlock A Folder Or A Parser.
description: 'Unlocking requires the `LockParsers` capability. It is only possible to unlock the highest locked object in a tree of locked objects. Unlocking recursively unlocks all of the objects children.
'
operationId: parsersUnlockById
parameters:
- name: id
in: path
description: The id of the folder or parser that needs to be unlocked.
required: true
schema:
type: string
responses:
'200':
description: Updated folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/move:
post:
tags:
- parsersLibraryManagement
summary: Move A Folder Or Parser.
description: 'Move a folder or parser.
'
operationId: parsersMove
parameters:
- name: id
in: path
description: Identifier of the folder or parser to move.
required: true
schema:
type: string
- name: parentId
in: query
description: Identifier of the parent folder to move the folder or parser to.
required: true
schema:
type: string
responses:
'200':
description: Moved folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/copy:
post:
tags:
- parsersLibraryManagement
summary: Copy A Folder Or Parser.
description: 'Copy a folder or parser.
'
operationId: parsersCopy
parameters:
- name: id
in: path
description: Identifier of the folder or parser to copy.
required: true
schema:
type: string
requestBody:
description: "Fields include:\n 1) Identifier of the parent folder to copy to.\n 2) Optionally provide a new name.\n 3) Optionally provide a new description.\n 4) Optionally set to true if you want to copy and preserved the locked status. Requires `LockParsers` capability.\n"
content:
application/json:
schema:
$ref: '#/components/schemas/ContentCopyParams'
required: true
responses:
'200':
description: Newly copied folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{id}/export:
get:
tags:
- parsersLibraryManagement
summary: Export A Folder Or Parser.
description: Export a folder or parser.
operationId: parsersExportItem
parameters:
- name: id
in: path
description: Identifier of the folder or parser to export.
required: true
schema:
type: string
- name: preserveLock
in: query
description: 'Set this to true if you want to export an object and preserve the locked status.
'
required: false
schema:
type: boolean
default: false
responses:
'200':
description: Exported folder or parser
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryExportBase'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/{parentId}/import:
post:
tags:
- parsersLibraryManagement
summary: Import A Folder Or Parser
description: 'Import a folder or parser
'
operationId: parsersImportItem
parameters:
- name: parentId
in: path
description: Identifier of the parent folder in which to import the folder or parser.
required: true
schema:
type: string
requestBody:
description: 'The folder or parser to be imported.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryExportBase'
required: true
responses:
'200':
description: Newly imported folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/path:
get:
tags:
- parsersLibraryManagement
summary: Read A Folder Or Parser By Its Path.
description: 'Read a folder or parser by its path.
'
operationId: parsersGetByPath
parameters:
- name: path
in: query
description: The path of the folder or parser.
required: true
schema:
type: string
responses:
'200':
description: Requested folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/parsers/search:
get:
tags:
- parsersLibraryManagement
summary: Search For Folders Or Parsers.
description: Search for a folder or parser in the cloud SIEM parsers library structure.
operationId: parsersSearch
parameters:
- name: query
in: query
description: "The search query to find folder or parsers. Below is the list of different filters with examples:\n - **createdBy** : Filter by the user's identifier who created the content. Example: `createdBy:000000000000968B`.\n - **createdBefore** : Filter by the content objects created before the given timestamp(in milliseconds). Example: `createdBefore:1457997222`.\n - **createdAfter** : Filter by the content objects created after the given timestamp(in milliseconds). Example: `createdAfter:1457997111`.\n - **modifiedBefore** : Filter by the content objects modified before the given timestamp(in milliseconds). Example: `modifiedBefore:1457997222`.\n - **modifiedAfter** : Filter by the content objects modified after the given timestamp(in milliseconds). Example: `modifiedAfter:1457997111`.\n - **type** : Filter by the type of the content object. Example: `type:folder`.\nYou can also use multiple filters in one query. For example to search for all content objects created by user with identifier 000000000000968B with creation timestamp after 1457997222 containing the text Test, the query would look like:\n `createdBy:000000000000968B createdAfter:1457997222 Test`"
required: true
schema:
type: string
example: createdBy:000000000000968B Test
- name: limit
in: query
description: Maximum number of items you want in the response.
required: false
schema:
type: integer
format: int32
example: 10
default: 100
- name: offset
in: query
description: The position or row from where to start the search operation.
required: false
schema:
type: integer
format: int32
example: 5
default: 0
responses:
'200':
description: List of folders and parsers matching the search query.
content:
application/json:
schema:
$ref: '#/components/schemas/ListParsersLibraryItemWithPath'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/system/parsers/{id}/lock:
post:
tags:
- parsersLibraryManagement
summary: Lock A Folder Or A Parser.
description: 'Locking requires the `LockParsers` capability. When an object is locked, it can''t be moved or deleted and only the local fields can be modified. Locking recursively locks all of the objects children.
'
operationId: systemParsersLockById
parameters:
- name: id
in: path
description: The id of the folder or parser that needs to be locked.
required: true
schema:
type: string
responses:
'200':
description: Updated folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/system/parsers/{id}/unlock:
post:
tags:
- parsersLibraryManagement
summary: Unlock A Folder Or A Parser.
description: 'Unlocking requires the `LockParsers` capability. It is only possible to unlock the highest locked object in a tree of locked objects. Unlocking recursively unlocks all of the objects children.
'
operationId: systemParsersUnlockById
parameters:
- name: id
in: path
description: The id of the folder or parser that needs to be unlocked.
required: true
schema:
type: string
responses:
'200':
description: Updated folder or parser.
content:
application/json:
schema:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
components:
schemas:
Path:
required:
- path
- pathItems
type: object
properties:
pathItems:
type: array
description: Elements of the path.
items:
$ref: '#/components/schemas/PathItem'
path:
type: string
description: String representation of the path.
IdToParsersLibraryBaseResponseMap:
maxProperties: 1000
type: object
additionalProperties:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
ParsersLibraryBaseUpdate:
required:
- description
- name
- version
type: object
properties:
name:
maxLength: 255
minLength: 1
type: string
description: Name of the folder or parser.
description:
maxLength: 4096
type: string
description: Description of the folder or parser.
version:
type: integer
description: Version of the folder or parser.
format: int64
type:
type: string
description: Type of the object model.
discriminator:
propertyName: type
ParsersLibraryFolderResponse:
allOf:
- $ref: '#/components/schemas/ParsersLibraryBaseResponse'
- required:
- children
type: object
properties:
children:
type: array
description: Children of the folder.
items:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
ParsersLibraryItemWithPath:
required:
- item
- path
type: object
properties:
item:
$ref: '#/components/schemas/ParsersLibraryBaseResponse'
path:
type: string
description: Path of the folder or parser.
example: /Parsers/SampleFolder/TestParser
ParsersLibraryExportBase:
required:
- description
- name
- type
type: object
properties:
name:
maxLength: 255
minLength: 1
type: string
description: Name of the folder or parser.
description:
maxLength: 4096
type: string
description: Description of the folder or parser.
type:
type: string
description: Type of the object model.
discriminator:
propertyName: type
PathItem:
required:
- id
- name
type: object
properties:
id:
type: string
description: Identifier of the path element.
name:
type: string
description: Name of the path element.
description:
type: string
description: Description of the path element.
ListParsersLibraryItemWithPath:
type: array
description: List of folders or parsers.
items:
$ref: '#/components/schemas/ParsersLibraryItemWithPath'
ErrorDescription:
required:
- code
- message
type: object
properties:
code:
type: string
description: An error code describing the type of error.
example: auth:password_too_short
message:
type: string
description: A short English-language description of the error.
example: Your password was too short.
detail:
type: string
description: An optional fuller English-language description of the error.
example: Your password was 5 characters long, the minimum length is 12 characters. See http://example.com/password for more information.
meta:
type: object
description: An optional list of metadata about the error.
example:
minLength: 12
actualLength: 5
ContentCopyParams:
required:
- parentId
type: object
properties:
parentId:
type: string
description: Identifier of the parent folder to copy to.
name:
type: string
description: Optionally provide a new name.
description:
type: string
description: Optionally provide a new description.
ErrorResponse:
required:
- errors
- id
type: object
properties:
id:
type: string
description: An identifier for the error; this is unique to the specific API request.
example: IUUQI-DGH5I-TJ045
errors:
type: array
description: A list of one or more causes of the error.
example:
- code: auth:password_too_short
message: Your password was too short.
- code: auth:password_character_classes
message: Your password did not contain any non-alphanumeric characters
items:
$ref: '#/components/schemas/ErrorDescription'
ParsersLibraryBaseResponse:
required:
- contentType
- createdAt
- createdBy
- description
- id
- isLocked
- isMutable
- isSystem
- modifiedAt
- modifiedBy
- name
- parentId
- type
- version
type: object
properties:
id:
type: string
description: Identifier of the folder or parser.
name:
type: string
description: Name of the folder or parser.
description:
type: string
description: Description of the folder or parser.
version:
type: integer
description: Version of the folder or parser.
format: int64
createdAt:
type: string
description: 'Creation timestamp in UTC in [RFC3339](https://tools.ietf.org/html/rfc3339) format.
'
format: date-time
createdBy:
type: string
description: Identifier of the user who created the resource.
modifiedAt:
type: string
description: Last modification timestamp in UTC.
format: date-time
modifiedBy:
type: string
description: Identifier of the user who last modified the resource.
parentId:
type: string
description: Identifier of the parent folder.
contentType:
type: string
description: "Type of the content. Valid values:\n 1) Folder\n 2) Parser\n"
type:
type: string
description: Type of the object model.
isLocked:
type: boolean
description: Whether the object is locked.
isSystem:
type: boolean
description: System objects are objects provided by Sumo Logic. System objects can only be localized. Non-local fields can't be updated.
isMutable:
type: boolean
description: Immutable objects are "READ-ONLY".
discriminator:
propertyName: type
ParsersLibraryBase:
required:
- description
- name
- type
type: object
properties:
name:
maxLength: 255
minLength: 1
type: string
description: Name of the folder or parser.
description:
maxLength: 4096
type: string
description: Description of the folder or parser.
type:
type: string
description: Type of the object model.
isLocked:
type: boolean
description: Locking/Unlocking requires the `LockParsers` capability. Locked objects can only be `Localized`. Updating or moving requires unlocking the object. Locking/Unlocking recursively locks all of the objects children. All children of a locked object must be locked.
default: false
discriminator:
propertyName: type
securitySchemes:
basicAuth:
type: http
scheme: basic
x-tagGroups:
- name: Archive Management
tags:
- archiveManagement
- name: Health Events
tags:
- healthEvents
- name: Infrequent Data Tier
tags:
- logSearchesEstimatedUsage
- name: Ingest Budgets Management V2
tags:
- ingestBudgetManagementV2
- name: Library Management
tags:
- appManagement
- appManagementV2
- contentManagement
- dashboardManagement
- folderManagement
- lookupManagement
- contentPermissions
- logSearchesManagement
- parsersLibraryManagement
- name: Metrics
tags:
- metricsSearchesManagement
- transformationRuleManagement
- metricsQuery
- metricsSearchesManagementV2
- name: Security Management
tags:
- accessKeyManagement
- oauthManagement
- accountManagement
- passwordPolicy
- policiesManagement
- samlConfigurationManagement
- serviceAllowlistManagement
- serviceAccountManagement
- scimUserManagement
- name: Organizations Management
tags:
- orgsManagement
- name: Settings Management
tags:
- connectionManagement
- dynamicParsingRuleManagement
- extractionRuleManagement
- fieldManagementV1
- partitionManagement
- scheduledViewManagement
- logsDataForwardingManagement
- dataDeletionRules
- name: Tokens Management
tags:
- tokensLibraryManagement
- name: Tracing
tags:
- traces
- spanAnalytics
- serviceMap
- name: Users and Roles Management
tags:
- roleManagement
- roleManagementV2
- userManagement
- name: Threat Intel Ingest Management
tags:
- threatIntelIngest
- threatIntelIngestProducer
- name: OpenTelemetry Collector Management
tags:
- otCollectorManagementExternal
- name: Source Template Management
tags:
- sourceTemplateManagementExternal
- name: Schema Base Management
tags:
- schemaBaseManagement
- name: Event Analytics Management
tags:
- eventAnalytics
- name: Budget Management
tags:
- budgetManagement
- name: Macro Management
tags:
- macroManagement
- name: Muting Schedules Management
tags:
- mutingSchedulesLibraryManagement
- name: SLO Management
tags:
- slosLibraryManagement
- name: Monitor Management
tags:
- monitorsLibraryManagement