New Metrics Searches Management API. Save metrics searches in the content library and organize them in a folder hierarchy. Allows you to list metrics searches under your personal folder.
openapi: 3.0.0
info:
title: Sumo Logic accessKeyManagement metricsSearchesManagementV2 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 <table>\n <tr>\n <td> <strong>Deployment</strong> </td>\n <td> <strong>Endpoint</strong> </td>\n </tr>\n <tr>\n <td> AU </td>\n <td> https://api.au.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> CA </td>\n <td> https://api.ca.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> DE </td>\n <td> https://api.de.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> EU </td>\n <td> https://api.eu.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> FED </td>\n <td> https://api.fed.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> IN </td>\n <td> https://api.in.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> JP </td>\n <td> https://api.jp.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> KR </td>\n <td> https://api.kr.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US1 </td>\n <td> https://api.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US2 </td>\n <td> https://api.us2.sumologic.com/api/ </td>\n </tr>\n </table>\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 \"<accessId>:<accessKey>\" -X GET https://api.<deployment>.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 `<accessId>:<accessKey>` to authenticate your HTTPS request. The following is an example request, replace the placeholder `<encoded>` with your encoded Access ID and Access Key string:\n ```bash\n curl -H \"Authorization: Basic <encoded>\" -X GET https://api.<deployment>.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 <table>\n <tr>\n <td> <strong>HTTP Status Code</strong> </td>\n <td> <strong>Error Code</strong> </td>\n <td> <strong>Description</strong> </td>\n </tr>\n <tr>\n <td> 301 </td>\n <td> moved </td>\n <td> 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.</td>\n </tr>\n <tr>\n <td> 401 </td>\n <td> unauthorized </td>\n <td> Credential could not be verified.</td>\n </tr>\n <tr>\n <td> 403 </td>\n <td> forbidden </td>\n <td> 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.</td>\n </tr>\n <tr>\n <td> 404 </td>\n <td> notfound </td>\n <td> Requested resource could not be found. </td>\n </tr>\n <tr>\n <td> 405 </td>\n <td> method.unsupported </td>\n <td> Unsupported method for URL. </td>\n </tr>\n <tr>\n <td> 415 </td>\n <td> contenttype.invalid </td>\n <td> Invalid content type. </td>\n </tr>\n <tr>\n <td> 429 </td>\n <td> rate.limit.exceeded </td>\n <td> The API request rate is higher than 4 request per second or inflight API requests are higher than 10 request per second. </td>\n </tr>\n <tr>\n <td> 500 </td>\n <td> internal.error </td>\n <td> Internal server error. </td>\n </tr>\n <tr>\n <td> 503 </td>\n <td> service.unavailable </td>\n <td> Service is currently unavailable. </td>\n </tr>\n </table>\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 \"<accessId>:<accessKey>\" https://api.<deployment>.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 \"<accessId>:<accessKey>\" https://api.<deployment>.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 \"<accessId>:<accessKey>\" https://api.<deployment>.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: metricsSearchesManagementV2
description: 'New Metrics Searches Management API.
Save metrics searches in the content library and organize them in a folder hierarchy. Allows you to list metrics searches under your personal folder.
'
x-displayName: Metrics Searches (New)
paths:
/v2/metricsSearches:
get:
tags:
- metricsSearchesManagementV2
summary: List All Metrics Search Pages.
description: List all metrics search pages under the Personal folder created by the user or under folders viewable by user.
operationId: ListMetricsSearches
parameters:
- name: limit
in: query
description: Limit the number of metric searches returned in the response. The number of metric searches returned may be less than the `limit`.
required: false
schema:
maximum: 100
minimum: 1
type: integer
format: int32
default: 50
example: 50
- name: token
in: query
description: Continuation token to get the next page of results. A page object with the next continuation token is returned in the response body. Subsequent GET requests should specify the continuation token to get the next page of results. `token` is set to null when no more pages are left.
required: false
schema:
type: string
example: GDCiRv4vebF3UWFJQ1kySXBOR3Bzh69GR0RyWm9vCtc
- name: mode
in: query
description: whether to list all viewable metric searches under the folders
required: false
schema:
pattern: ^(createdByUser|allViewableByUser)$
type: string
example: createdByUser
x-pattern-message: Must be `createdByUser` or `allViewableByUser`
example: createdByUser
responses:
'200':
description: Paginated list of metrics search pages under the Personal folder created by the user or viewable by user.
content:
application/json:
schema:
$ref: '#/components/schemas/PaginatedMetricsSearches'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- metricsSearchesManagementV2
summary: Create A New Metrics Search Page.
description: Creates a new metrics search page.
operationId: createMetricsSearches
requestBody:
description: Information to create the new metrics search page.
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSearchRequest'
required: true
responses:
'200':
description: The metrics search page has been created.
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSearchResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v2/metricsSearches/{id}:
get:
tags:
- metricsSearchesManagementV2
summary: Get A Metrics Search Page.
description: Get a metrics search page by the given identifier.
operationId: getMetricsSearches
parameters:
- name: id
in: path
description: Unique identifier of the metrics search page to return.
required: true
schema:
type: string
responses:
'200':
description: Metrics search page that was requested.
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSearchResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- metricsSearchesManagementV2
summary: Update A Metrics Search Page.
description: Update a metrics search page by the given identifier.
operationId: updateMetricsSearches
parameters:
- name: id
in: path
description: Unique identifier of the metrics search page to return.
required: true
schema:
type: string
requestBody:
description: Information to update the metrics search page.
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSearchRequest'
required: true
responses:
'200':
description: The metrics search page was successfully modified.
content:
application/json:
schema:
$ref: '#/components/schemas/MetricsSearchResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- metricsSearchesManagementV2
summary: Delete A Metrics Search Page.
description: Delete metrics search page by the given identifier.
operationId: deleteMetricsSearches
parameters:
- name: id
in: path
description: Unique identifier of the metrics search page to delete.
required: true
schema:
type: string
responses:
'204':
description: Metrics search page was deleted successfully.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
components:
schemas:
MetricsQueryData:
required:
- filters
- metric
type: object
properties:
metric:
type: string
description: The metric of the query.
example: CPU_user
aggregationType:
pattern: ^(Count|Minimum|Maximum|Sum|Average|None)$|^$
type: string
description: The type of aggregation. Can be `Count`, `Minimum`, `Maximum`, `Sum`, `Average` or `None`.
example: Count
x-pattern-message: Must be `Count`, `Minimum`, `Maximum`, `Sum`, `Average` or `None`
groupBy:
type: string
description: The field to group the results by.
example: _sourceHost
filters:
type: array
description: A list of filters for the metrics query.
items:
$ref: '#/components/schemas/MetricsFilter'
operators:
type: array
description: A list of operator data for the metrics query.
items:
$ref: '#/components/schemas/OperatorData'
description: The data format describing a basic metrics query.
example:
metric: CPU_user
aggregationType: count
groupBy: _sourceHost
filters:
- key: _sourceCategory
value: kubernetes
- key: _sourceHost
value: dep-kubernetes-1
operators:
operatorName: avg
parameters:
- key: aggregator
value: max
- key: operation
value: ''
- key: value
value: 50
OperatorParameter:
required:
- key
- value
type: object
properties:
key:
type: string
description: The key of the operator parameter.
example: operation
value:
type: string
description: The value of the operator parameter.
example: '>'
description: The operator parameter for operator data.
example:
key: aggregator
value: max
PaginatedMetricsSearches:
required:
- metricsSearches
type: object
properties:
metricsSearches:
type: array
description: List of metrics search pages.
items:
$ref: '#/components/schemas/MetricsSearchResponse'
next:
type: string
description: Next continuation token. `token` is set to null when no more pages are left.
example: GDCiRv4vebF3UWFJQ1kySXBOR3Bzh69GR0RyWm9vCtc
SpansQueryData:
required:
- filters
- groupBy
- limit
- visualizations
type: object
properties:
filters:
type: array
description: A list of filters for the spans query.
items:
$ref: '#/components/schemas/SpansFilter'
visualizations:
type: array
description: A list of used visualization methods for the spans query.
items:
$ref: '#/components/schemas/SpansVisualization'
groupBy:
type: array
description: A list of group-by clauses for the spans query.
items:
$ref: '#/components/schemas/SpansGroupBy'
limit:
type: array
description: A list of limits that will be applied to the spans query.
items:
$ref: '#/components/schemas/SpansLimitItem'
description: The data format describing a basic spans query.
SpansVisualization:
required:
- name
- type
type: object
properties:
type:
pattern: ^(count|calculation)$
type: string
description: The visualization type.
example: count
x-pattern-message: Must be `count` or `calculation`
name:
type: string
description: A unique name of the visualization.
example: duration_pct_95
discriminator:
propertyName: type
mapping:
count: '#/components/schemas/SpansCountVisualization'
calculation: '#/components/schemas/SpansCalculationVisualization'
MetricsSearch:
required:
- queries
- timeRange
- title
type: object
properties:
title:
maxLength: 255
minLength: 1
pattern: ^\s*\S.*$
type: string
description: Title of the metrics search page.
x-pattern-message: must contain at least 1 non-whitespace character
timeRange:
$ref: '#/components/schemas/ResolvableTimeRange'
description:
type: string
description: Description of the metrics search page.
queries:
type: array
description: Queries of the metrics search page.
items:
$ref: '#/components/schemas/Query'
visualSettings:
type: string
description: Visual settings of the metrics search page.
TracesQueryData:
required:
- filters
type: object
properties:
filters:
type: array
description: A list of filters for the traces query.
items:
$ref: '#/components/schemas/TracesFilter'
description: The data format describing a basic traces query.
MetricsFilter:
required:
- value
type: object
properties:
key:
type: string
description: The key of the metrics filter.
example: _sourceCategory
value:
type: string
description: The value of the metrics filter.
example: kubernetes
negation:
type: boolean
description: Whether or not the metrics filter is negated.
example: false
description: The filter for metrics query.
example:
key: _sourceCategory
value: cqmerger
negation: false
Query:
required:
- queryKey
- queryString
- queryType
type: object
properties:
queryString:
type: string
description: The metrics, traces or logs query.
example: _sourceCategory=cqsplitter metric=CPU_user | count by _sourceHost
queryType:
pattern: ^(Logs|Metrics|Traces|Spans)$
type: string
description: The type of the query, either `Metrics`, `Traces`, `Spans` or `Logs`.
example: Logs
x-pattern-message: Must be `Logs`, `Traces`, `Spans` or `Metrics`
queryKey:
type: string
description: 'The key for metric, traces or log queries. Used as an identifier for queries. It is displayed on the panel builder and used for display overrides and query toggling.
'
example: A
metricsQueryMode:
pattern: ^(Basic|Advanced|basic|advanced)$
type: string
description: 'The mode of the metrics query that the user was editing. Can be `Basic` or `Advanced`. Will ONLY be specified for metrics queries.
'
example: Basic
x-pattern-message: Must be `Basic`, or `Advanced`
metricsQueryData:
$ref: '#/components/schemas/MetricsQueryData'
tracesQueryData:
$ref: '#/components/schemas/TracesQueryData'
spansQueryData:
$ref: '#/components/schemas/SpansQueryData'
parseMode:
pattern: ^(Auto|Manual|Intelliparse)$
type: string
description: "This field only applies for queryType of `Logs` but other query types may be supported in the future. Define the parsing mode to scan the JSON format log messages. Possible values are:\n 1. `Auto`\n 2. `Manual`\nIn AutoParse mode, the system automatically figures out fields to parse based on the search query. While in the Manual mode, no fields are parsed out automatically. For more information see [Dynamic Parsing](https://help.sumologic.com/?cid=0011)."
example: Auto
default: Auto
x-pattern-message: Must be either `Auto`,`Manual` or `Intelliparse`
timeSource:
pattern: ^(Message|Receipt|Searchable)$
type: string
description: This field only applies for queryType of `Logs` but other query types may be supported in the future. Define the time source of this query. Possible values are `Message`, `Receipt`. `Message` will use the timeStamp on the message, while `Receipt` will use the timestamp it was received by Sumo.
example: Message
default: Message
x-pattern-message: Must be `Message`, or `Receipt`
transient:
type: boolean
description: This field only applies for queryType of `Metrics` but other query types may be supported in the future. Determines if the row should be returned in the response. Can be used in conjunction with a join, if only the result of the join is needed, and not the intermediate rows. Setting `transient` to `true` wherever the intermediate results aren't required speeds up the computation and reduces the amount of data transferred over the network.
default: false
outputCardinalityLimit:
maximum: 3000
minimum: 1
type: integer
description: This field only applies for queryType of `Metrics` but other query types may be supported in the future. Specifies the output cardinality limitations for the query, which is the maximum number of timeseries returned in the result.
format: int32
example: 1000
default: 1000
TracesFilter:
required:
- type
type: object
properties:
type:
pattern: ^(FieldDescriptor|DurationMetricDescriptor|NumericMetricDescriptor|CPCOfFilterDescriptor|MaxCPCOfFilterDescriptor|MaxCPCFilterDescriptor)$|^$
type: string
description: The type of the filter.
example: FieldDescriptor
x-pattern-message: Must be `FieldDescriptor`, `DurationMetricDescriptor`, `NumericMetricDescriptor`, `CPCOfFilterDescriptor`, `MaxCPCOfFilterDescriptor` or `MaxCPCFilterDescriptor`
description: The filter for traces query.
discriminator:
propertyName: type
OperatorData:
required:
- operatorName
- parameters
type: object
properties:
operatorName:
type: string
description: The name of the metrics operator.
example: avg
parameters:
type: array
description: A list of operator parameters for the operator data.
items:
$ref: '#/components/schemas/OperatorParameter'
description: The operator data for metrics query.
example:
operatorName: avg
parameters:
- key: aggregator
value: max
- key: operation
value: ''
- key: value
value: 50
SpansLimitItem:
required:
- direction
- limitValue
type: object
properties:
direction:
pattern: ^(asc|desc)$
type: string
description: Describes whether the results should be sorted in an ascending or a descending order.
example: asc
x-pattern-message: Must be `asc` or `desc`
limitValue:
type: integer
description: 'The number of aggregated results returned, e.g. if 10 is requested, then only the first 10 aggregated results are returned.
'
format: int32
example: 10
description: 'A representation of the limit operator which reduces the number of aggregate results returned: either the top k results or bottom k results.
'
ResolvableTimeRange:
required:
- type
type: object
properties:
type:
type: string
description: Type of the time range. Value must be either `CompleteLiteralTimeRange` or `BeginBoundedTimeRange`.
example:
type: BeginBoundedTimeRange
from:
type: RelativeTimeRangeBoundary
relativeTime: -15m
discriminator:
propertyName: type
SpansFilter:
required:
- fieldName
- type
type: object
properties:
type:
pattern: ^(StandaloneKey|KeyValuePair)$
type: string
description: The spans filter type.
example: StandaloneKey
x-pattern-message: Must be `StandaloneKey` or `KeyValuePair`.
fieldName:
type: string
description: The name of the filtering field.
example: service
discriminator:
propertyName: type
mapping:
StandaloneKey: '#/components/schemas/SpansFilterStandaloneKey'
KeyValuePair: '#/components/schemas/SpansFilterKeyValuePair'
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
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'
MetricsSearchResponse:
allOf:
- $ref: '#/components/schemas/MetricsSearchRequest'
- type: object
properties:
id:
type: string
description: Unique identifier for the metrics search page.
example: B23OjNs5ZCyn5VdMwOBoLo3PjgRnJSAlNTKEDAcpuDG2CIgRe9KFXMofm2H2
SpansGroupBy:
required:
- type
type: object
properties:
type:
pattern: ^(time|field)$
type: string
description: The type of the group-by clause.
example: time
x-pattern-message: Must be `time` or `field`
discriminator:
propertyName: type
mapping:
time: '#/components/schemas/SpansTimeGroupBy'
field: '#/components/schemas/SpansFieldGroupBy'
MetricsSearchRequest:
allOf:
- $ref: '#/components/schemas/MetricsSearch'
- type: object
properties:
folderId:
# --- truncated at 32 KB (34 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/sumo-logic/refs/heads/main/openapi/sumo-logic-metricssearchesmanagementv2-api-openapi.yml