openapi: 3.0.0
info:
title: Sumo Logic accessKeyManagement traces 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: traces
description: 'Traces API
The Traces API allows you to browse traces collected in the system. You can execute queries to find traces matching provided search criteria as well as gather detailed information about individual traces and spans. For more information, see [View and investigate traces](https://help.sumologic.com/docs/apm/traces/view-and-investigate-traces).
'
x-displayName: Traces
paths:
/v1/tracing/tracequery:
post:
tags:
- traces
summary: Run A Trace Search Query Asynchronously.
description: Execute a trace search query and get the id to fetch its status and results. Use the [Trace Query Status](#operation/getTraceQueryStatus) endpoint to check a query status. When the query has been completed, use the [Trace Query Result](#operation/getTraceQueryResult) endpoint to get the result of the asynchronous query.
operationId: createTraceQuery
parameters: []
requestBody:
description: Query parameters.
content:
application/json:
schema:
$ref: '#/components/schemas/AsyncTraceQueryRequest'
required: true
responses:
'200':
description: Query execution result.
content:
application/json:
schema:
$ref: '#/components/schemas/CreateTraceQueryResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/tracequery/{queryId}:
delete:
tags:
- traces
summary: Cancel A Trace Search Query.
description: Cancel a currently processed trace search query with the given id.
operationId: cancelTraceQuery
parameters:
- name: queryId
in: path
description: Identifier of the query to cancel.
required: true
schema:
type: string
example: 798a13dc1ceeb19a
responses:
'204':
description: Query canceled successfully.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/tracequery/{queryId}/status:
get:
tags:
- traces
summary: Get A Trace Search Query Status.
description: Get a status of a trace query with the given id. When the query has been completed, use the [Trace Query Result](#operation/getTraceQueryResult) endpoint to get the result of the asynchronous query.
operationId: getTraceQueryStatus
parameters:
- name: queryId
in: path
description: Identifier of the executed query.
required: true
schema:
type: string
example: 195038749d21ad109242c95cbbc8709d
responses:
'200':
description: Status of the given trace search query.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceQueryStatusResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/tracequery/{queryId}/rows/{rowId}/traces:
get:
tags:
- traces
summary: Get Results Of A Trace Search Query.
description: Get a list of traces matching a query with the specified id. The response is paginated with a default limit of 100 traces per page.
operationId: getTraceQueryResult
parameters:
- name: queryId
in: path
description: Identifier of the executed query.
required: true
schema:
type: string
example: 195038749d21ad109242c95cbbc8709d
- name: rowId
in: path
description: Identifier of the query row.
required: true
schema:
type: string
example: A
- name: limit
in: query
description: Limit of the number of traces returned in the response.
required: false
schema:
maximum: 500
minimum: 1
type: integer
format: int32
example: 100
default: 100
- 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: dlFXd0lhSkxzRjAwYnpVZkMrRmlhYnF4cGtNMWdnVEI
responses:
'200':
description: Details about the given span query.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceQueryResultResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/metrics:
get:
tags:
- traces
summary: Get Trace Search Query Metrics.
description: Get a list of available trace metrics that can be used in trace search queries.
operationId: getMetrics
parameters: []
responses:
'200':
description: List of available metrics.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceMetricsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/tracequery/fields:
get:
tags:
- traces
summary: Get Filter Fields For Trace Search Queries.
description: Get a list of available fields which can be used in trace search queries.
operationId: getTraceQueryFields
parameters: []
responses:
'200':
description: List of available fields.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceFieldsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/tracequery/fields/{field}/values:
get:
tags:
- traces
summary: Get Trace Search Query Filter Field Values.
description: Get a list of available values for the given trace search query filter field. Not all fields support value listing. The response is paginated with a default limit of 10 values per page.
operationId: getTraceQueryFieldValues
parameters:
- name: field
in: path
description: Field identifier.
required: true
schema:
type: string
- name: query
in: query
description: Search filter to apply on the values to be returned. Only values containing the search query term will be returned.
required: false
schema:
type: string
- name: limit
in: query
description: The maximum number of results to fetch.
required: false
schema:
maximum: 500
minimum: 1
type: integer
format: int32
default: 10
- 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
- name: fieldType
in: query
description: 'Indicates the kind of a field. Possible values: `SpanAttribute`, `SpanEventAttribute`.'
required: false
schema:
pattern: ^(SpanAttribute|SpanEventAttribute)$
type: string
example: SpanEventAttribute
x-pattern-message: 'Should be one of: `SpanAttribute`, `SpanEventAttribute`.'
responses:
'200':
description: List of available filter values for the given field.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceFieldValuesResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}:
get:
tags:
- traces
summary: Get Trace Details.
description: Get details of a trace with the given identifier.
operationId: getTrace
parameters:
- name: traceId
in: path
description: Identifier of the trace to get the details.
required: true
schema:
type: string
responses:
'200':
description: Details of the trace with the given identifier.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceDetail'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/exists:
get:
tags:
- traces
summary: Check If The Trace Exists.
description: Check if the trace with the given identifier exists.
operationId: traceExists
parameters:
- name: traceId
in: path
description: Identifier of the trace to check.
required: true
schema:
type: string
responses:
'200':
description: The response contains the information whether the trace exists with other optional attributes.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceExistsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/spans:
get:
tags:
- traces
summary: Get A List Of Trace Spans.
description: Get a list of spans for the given trace. The response is paginated with a default limit of 100 spans per page.
operationId: getSpans
parameters:
- name: traceId
in: path
description: Identifier of the trace to get the spans.
required: true
schema:
type: string
- name: limit
in: query
description: The maximum number of results to fetch.
required: false
schema:
maximum: 500
minimum: 1
type: integer
format: int32
default: 100
- 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
responses:
'200':
description: List of spans for the given trace.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceSpansResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/traceEvents:
get:
tags:
- traces
summary: Get A List Of Events (without Their Attributes) Per Span For A Trace.
description: Gets a list of the events (without their attributes) attached to each span in a given trace. The response is paginated with a default limit of 100 spans per page.
operationId: getTraceLightEvents
parameters:
- name: traceId
in: path
description: Identifier of the trace for which span events will be returned.
required: true
schema:
maxLength: 32
minLength: 16
type: string
example: 695068749d21cd104222a95cabc4707c
- name: limit
in: query
description: The maximum number of spans with events returned by a single query.
required: false
schema:
maximum: 500
minimum: 1
type: integer
format: int32
default: 100
- 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: dlFXd0lhSkxzRjAwYnpVZkMrRmlhYnF4cGtNMWdnVEI
responses:
'200':
description: Map of spans to events relations.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceLightEventsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/criticalPath:
get:
tags:
- traces
summary: Get A Critical Path Of A Trace.
description: Get a list of span segments composing the critical path of the trace. A span segment represents the processing time that was consumed within the span itself and does not incorporate the processing time of its children. The critical path is the sequence of span segments that contribute to the total trace duration. An increase of the processing time of any segment from the critical path would result in an increase of the total trace processing time.
operationId: getCriticalPath
parameters:
- name: traceId
in: path
description: Identifier of the trace.
required: true
schema:
type: string
- name: limit
in: query
description: The maximum number of results to fetch.
required: false
schema:
maximum: 500
minimum: 1
type: integer
format: int32
default: 100
- 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
responses:
'200':
description: List of span segments composing the critical path.
content:
application/json:
schema:
$ref: '#/components/schemas/CriticalPathResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/criticalPath/breakdown/service:
get:
tags:
- traces
summary: Get A Critical Path Service Breakdown Of A Trace.
description: Get a critical path breakdown by services of the spans contributing to the critical path of a trace with the given identifier.
operationId: getCriticalPathServiceBreakdown
parameters:
- name: traceId
in: path
description: Identifier of the trace.
required: true
schema:
type: string
responses:
'200':
description: List of elements representing the critical path service breakdown.
content:
application/json:
schema:
$ref: '#/components/schemas/CriticalPathServiceBreakdownResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/spans/{spanId}:
get:
tags:
- traces
summary: Get Span Details.
description: Get details of a span with the given identifier.
operationId: getSpan
parameters:
- name: traceId
in: path
description: Identifier of the trace the span belongs to.
required: true
schema:
type: string
- name: spanId
in: path
description: Identifier of the span to get the details.
required: true
schema:
type: string
responses:
'200':
description: Details of the span with the given identifier.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceSpanDetail'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/tracing/traces/{traceId}/spans/{spanId}/billingInfo:
get:
tags:
- traces
summary: Get Span Billing Details.
description: Get the billing information of the span.
operationId: getSpanBillingInfo
parameters:
- name: traceId
in: path
description: Identifier of the trace the span belongs to.
required: true
schema:
type: string
- name: spanId
in: path
description: Identifier of the span to get the billing info.
required: true
schema:
type: string
responses:
'200':
description: Billing information of the span with the given identifier.
content:
application/json:
schema:
$ref: '#/components/schemas/TraceSpanBillingInfo'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
components:
schemas:
CriticalPathServiceBreakdownElementBase:
required:
- duration
type: object
properties:
service:
type: string
description: The name of the service.
example: user-service
serviceColor:
type: string
description: Color hex code assigned to the service.
example: '#fa41c6'
duration:
type: integer
description: Overall processing time in nanoseconds consumed by the spans belonging to this service in the critical path (a sum of the duration times of the spans' critical path segments).
format: int64
example: 12957153
SpanEventAttribute:
type: object
properties:
attributeName:
type: string
description: Name of the attribute.
example: message_details
attributeValue:
$ref: '#/components/schemas/EventAttributeValue'
TraceSpanDetail:
allOf:
- $ref: '#/components/schemas/TraceSpan'
- type: object
properties:
errorMessage:
type: string
description: Produced error message (could be a stack trace, database error code, ..)
example: "Exception in thread \"local[9]\" java.lang.OutOfMemoryError: Java heap space\n at my.app.force.fields.SpaceShipForceField.main(SpaceShipForceField.java:17)\n"
fields:
type: object
additionalProperties:
$ref: '#/components/schemas/TracingValue'
description: Fields attached to this span.
example:
component:
type: StringTracingValue
value: http
http.request.method:
type: StringTracingValue
value: GET
url.full:
type: StringTracingValue
value: https://example.com/v1/users/123
http.response.status_code:
type: StringTracingValue
value: '200'
criticalPathContribution:
$ref: '#/components/schemas/TraceSpanCriticalPathContribution'
logs:
type: array
description: Logs attached to this span.
example:
- '[19/Dec/2019:10:58:21 +0000] ''GET /v1/users/123 HTTP/1.1'' 200 8215 ''http://111.111.11.1/'' ''Mozilla/5.0 (Macintosh; Intel Mac OS X 11_11_1) AppleWebKit/111.11 (KHTML, like Gecko) Chrome/11.1.1111.11 Safari/111.11'''
- '[19/Dec/2019:10:58:24 +0000] ''GET /logo.png HTTP/1.1'' 404 555 ''http://111.111.11.1/'' ''Mozilla/5.0 (Macintosh; Intel Mac OS X 11_11_1) AppleWebKit/111.11 (KHTML, like Gecko) Chrome/11.1.1111.11 Safari/111.11'''
items:
type: string
events:
type: array
description: Events attached to this span.
items:
$ref: '#/components/schemas/SpanEvent'
links:
type: array
description: List of casually related spans.
items:
$ref: '#/components/schemas/SpanLink'
AsyncTraceQueryRow:
required:
- query
- rowId
type: object
properties:
query:
$ref: '#/components/schemas/TraceQueryExpression'
rowId:
maxLength: 16
type: string
description: An identifier used to reference this particular row of the query request while fetching a query result. Within a query, row ids must have distinct values.
example: '#A'
orderBy:
$ref: '#/components/schemas/OrderBy'
ServiceType:
pattern: ^(Db|HTTP|MQ|Web|Mixed|Unknown|Cpp|DotNET|Erlang|Go|Java|NodeJS|Php|Python|Ruby|WebJS|Swift|MSSQL|MySQL|Oracle|Db2|PostgreSQL|Redshift|Hive|Cloudscape|HSQLDB|Progress|MaxDB|HANADB|Ingres|FirstSQL|EnterpriseDB|Cache|Adabas|Firebird|ApacheDerby|FileMaker|Informix|InstantDB|InterBase|MariaDB|Netezza|PervasivePSQL|PointBase|SQLite|Sybase|Teradata|Vertica|H2|ColdFusion|Cassandra|HBase|MongoDB|Redis|Couchbase|CouchDB|CosmosDB|DynamoDB|Neo4j|Geode|Elasticsearch|Memcached|CockroachDB|RPC|gRPC|JavaRMI|DotNETWCF|ApacheDubbo)$
type: string
description: Defines type of service.
example: HTTP
x-pattern-message: Should be either `Db`, `HTTP`, `MQ`, `Web`, `Mixed`, `Unknown`, `Cpp`, `DotNET`, `Erlang`, `Go`, `Java`, `NodeJS`, `Php`, `Python`, `Ruby`, `WebJS`, `Swift`, `MSSQL`, `MySQL`, `Oracle`, `Db2`, `PostgreSQL`, `Redshift`, `Hive`, `Cloudscape`, `HSQLDB`, `Progress`, `MaxDB`, `HANADB`, `Ingres`, `FirstSQL`, `EnterpriseDB`, `Cache`, `Adabas`, `Firebird`, `ApacheDerby`, `FileMaker`, `Informix`, `InstantDB`, `InterBase`, `MariaDB`, `Netezza`, `PervasivePSQL`, `PointBase`, `SQLite`, `Sybase`, `Teradata`, `Vertica`, `H2`, `ColdFusion`, `Cassandra`, `HBase`, `MongoDB`, `Redis`, `Couchbase`, `CouchDB`, `CosmosDB`, `DynamoDB`, `Neo4j`, `Geode`, `Elasticsearch`, `Memcached`, `CockroachDB`, `RPC`, `gRPC`, `JavaRMI`, `DotNETWCF` or `ApacheDubbo`
DoubleTracingValue:
allOf:
- $ref: '#/components/schemas/TracingValue'
- required:
- value
type: object
properties:
value:
type: number
format: double
TraceFieldsResponse:
required:
- fields
type: object
properties:
fields:
type: array
description: List of filter fields.
items:
$ref: '#/components/schemas/TraceFieldDetail'
OrderBy:
required:
- fieldName
- order
type: object
properties:
fieldName:
maxLength: 32
minLength: 1
type: string
description: 'Field based on which results should be sorted. When not provided, the default behavior is to sort by timestamp descending. Sortable fields values: `trace_id`, `start_timestamp`, `duration`, `spans_number`, `errors`, `status_code`.'
example: start_timestamp
order:
pattern: ^(Asc|Desc)$
type: string
description: Type of sorting values - descending or ascending.
example: Asc
default: Desc
x-pattern-message: should be either 'Asc' or 'Desc'
TraceFieldDetail:
required:
- field
- fieldType
- type
type: object
properties:
field:
type: string
description: Filter field name.
example: operation
fieldType:
pattern: ^(SpanAttribute|SpanEventAttribute)$
type: string
description: 'Indicates the kind of a field. Possible values: `SpanAttribute`, `SpanEventAttribute`.'
example: SpanEventAttribute
default: SpanAttribute
x-pattern-message: 'Should be one of: `SpanAttribute`, `SpanEventAttribute`.'
valueListing:
type: boolean
description: Indicates whether values for this field can be listed.
example: false
description:
type: string
description: Short description of the field.
example: A piece of the workflow represented by a span
type:
type: string
description: 'The type the values of this field will have. Possible values: `DoubleTracingValue`, `IntegerTracingValue`, `StringTracingValue`, `DateTimeTracingValue`.'
example: StringTracingValue
noValuesReason:
$ref: '#/components/schemas/NoTraceFieldValuesReason'
TraceFieldValuesResponse:
required:
- fieldValues
- totalCount
type: object
properties:
fieldValues:
type: array
description: List of filter field values.
items:
type: string
totalCount:
type: integer
description: Total number of values for a field matching the query. Can be approximated when it's above 3000.
format: int64
example: 1234
next:
type: string
description: Next continuation token.
example: Mi93V0ZqTTBzaW89
AsyncTraceQueryRequest:
required:
- queryRows
- timeRange
type: object
properties:
queryRows:
type: array
description: A list of trace queries.
items:
$ref: '#/components/schemas/AsyncTraceQueryRow'
timeRange:
$ref: '#/components/schemas/ResolvableTimeRange'
TraceLightEventsResponse:
type: object
properties:
spanEvents:
maxProperties: 1000
type: object
additionalProperties:
type: array
items:
$ref: '#/components/schemas/LightSpanEvent'
description: Map of span ids to lists of their events, without their attributes.
next:
type: string
description: Next continuation token.
example: dlFXd0lhSkxzRjAwYnpVZkMrRmlhYnF4cGtNMWdnVEI
SpanLink:
required:
- spanId
- traceId
type: object
properties:
traceId:
type: string
description: Trace identifier of the linked span.
example: 00000000002317A9
spanId:
type: string
description: Span identifier of the linked span.
example: 000000000003C7BE
description: Details of the linked span.
TraceDetail:
required:
- id
type: object
properties:
id:
type: string
description: Trace identifier.
example: 00000000000120CB
rootService:
type: string
description: 'Root service which started the trace. Examples: `user-service`, `authentication-service`, `payment-service`, `/shopping-cart`'
example: user-service
rootResource:
type: string
description: 'Root resource on which the trace was started. Examples: `db.query`, `http.request`, `rpc.call`, `container`'
example: http.request
rootStatus:
$ref: '#/components/schemas/TraceSpanStatus'
rootOperationName:
type: string
description: The name of the operation given to the root span.
example: retrieveAccount
metrics:
maxProperties: 1000
type: object
additionalProperties:
$ref: '#/components/schemas/DoubleTracingValue'
description: Calculated trace metrics.
example:
_duration: 143984411
startedAt:
type: string
description: Date and time the trace was started in [ISO 8601 / RFC3339](https://tools.ietf.org/html/rfc3339) format.
format: date-time
example: 2019-11-22 09:00:00+00:00
criticalPathServiceBreakdownSummary:
$ref: '#/components/schemas/CriticalPathServiceBreakdownSummary'
CreateTraceQueryResponse:
required:
- queryId
type: object
properties:
queryId:
type: string
description: Id of the created query
example: cafaebf2f4f8320f
TraceSpanStatus:
required:
- code
type: object
properties:
code:
type: string
description: 'Status code of the span. Possible values: `OK`, `ERROR`, `UNKNOWN`.'
example: OK
message:
type: string
description: Optional descriptive message about the status, could be an http status code or the kind of an error, e.g. OSError.
example: '404'
CriticalPathServiceBreakdownSummary:
required:
- elements
- idleTime
- otherServicesDuration
type: object
properties:
elements:
type: array
description: List of the elements representing the critical path service duration breakdown - contains the first few services with the longest overall duration of the spans contributing to the critical path.
items:
$ref: '#/components/schemas/CriticalPathServiceBreakdownElementBase'
otherServicesDuration:
type: integer
description: Overall processing time in nanoseconds consumed by the rest of the spans in the critical path (a sum of the duration times of the spans' critical path segments).
format: int64
example: 12957153
idleTime:
type: integer
description: Overall time in nanoseconds when no particular operation was in progress.
format: int64
example: 60000000
SpanPathSegment:
required:
- duration
- ratio
- spanId
- startOffset
type: object
properties:
spanId:
type: string
description: Span identifier.
example: 00000000000120CB
service:
type: string
description: The name of the service this span is part of.
example: user-service
serviceColor:
type: string
description: Color hex code assigned to the service.
example: '#fa41c6'
startOffset:
type: integer
description: Number of nanoseconds from the span startedAt the segment started.
format: int64
example: 311285715
duration:
type: integer
description: Number of nanoseconds the span segment lasted.
format: int64
example: 12957153
fraction:
type: number
description: The fraction (value between 0.0 and 1.0) from the trace duration time this segment took.
format: double
example: 0.4
TraceQueryStatusResponse:
required:
- queryRows
- status
type: object
properties:
queryRows:
type: array
description: A list of trace queries.
items:
$ref: '#/components/schemas/TraceQueryRowStatus'
status:
pattern: ^(Processing|Finished|Error|Canceled)$
type: string
description: 'Status of the query. Possible values: `Processing`, `Finished`, `Error`, `Canceled`.'
example: Processing
x-pattern-message: Should be either `Processing`, `Finished`, `Error`, `Canceled`.
LightSpanEvent:
required:
- name
- timestamp
type: object
properties:
timestamp:
type: string
description: Time when an event happened in the [ISO 8601 / RFC3339](https://tools.ietf.org/html/rfc3339) format.
format: date-time
example: 2021-04-19 17:36:57.476230+00:00
name:
type: string
description: Name of the event.
example: domContentLoadedEventStart
description: Light version of Span Event, without the attributes.
TraceQueryExpression:
required:
- type
type: object
properties:
type:
type: string
description: Expression type of the object model.
description: Base query expression object.
discriminator:
propertyName: type
NoTraceFieldValuesReason:
required:
- code
- message
type: object
properties:
code:
pattern: ^(HighCardinalityField|AutocompleteDisabled)$
type: string
description: 'A code uniquely identifying the reason for the lack of trace field values. Possible values: `HighCardinalityField`, `AutocompleteDisabled`.'
example: HighCardinalityField
x-pattern-message: Should be either `HighCardinalityField`, `AutocompleteDisabled`.
message:
type: string
description: A short English-language description of the reason.
example: Autocomplete has been disabled for this field due to high cardinality.
TraceSpanBillingInfo:
required:
- billedBytes
- billedFormat
type: object
properties:
billedBytes:
type: integer
description: Number of bytes that were charged for the span.
example: 529
billedFormat:
type: string
description: Billing format of the span. Number of bytes of this representation of the span is equal to `billedBytes`.
example: traceId=2ff9c457b1aa00f4;spanId=97872e33215c4275;parentSpanId=98bcdfc5da874c40;operation=spanId-97872e33215c4275;startTimestamp=1603283111874000000;endTimestamp=1603283112268000000;service=ServiceA;status.code=ERROR;status.message=ERROR;kind=SERVER;custom-tag-2=value2;_sourcehost=127.0.0.1;url.full=https://example.com/api/operation-x;message=Some error message;_sourcecategory=Http Input;custom-tag-1=value1;error=true;_sourcename=Http Input;error.kind=InvalidInput;_collector=trace-generator-collector;http.request.method=GET;
TraceSpanInfo:
required:
- type
type: object
properties:
type:
type: string
description: 'Type of this span. Possible values: `TraceHttpSpanInfo`, `TraceDbSpanInfo`, `TraceMessageBusSpanInfo`.'
example: TraceHttpSpanInfo
discriminator:
propertyName: type
SpanEvent:
description: Span event containing all information (in particular attributes).
allOf:
- $ref: '#/components/schemas/LightSpanEvent'
- type: object
properties:
attributes:
type: array
description: Span event attributes.
items:
$ref: '#/components/schemas/SpanEventAttribute'
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
TraceSpan:
required:
- duration
- id
- operationName
- startedAt
- status
type: object
properties:
id:
type: string
description: Identifier of the span.
example: 00000000002317A9
parentId:
type: string
description: Identifier of the parent span, if any. If the span has no parent it's considered a root span.
example: 000000000003C7BE
operationName:
type: string
description: The name of the operation given to the span.
example: retrieveAccount
resource:
type: string
description: The name of the resource attached to the span.
example: http.request
service:
type: string
description: The name of the service this span is part of.
example: user-service
serviceColor:
type: string
description: Color hex code assigned to the service.
example: '#fa41c6'
serviceType:
$ref: '#/components/schemas/ServiceType'
duration:
type: integer
description: Number of nanoseconds the span lasted.
format: int64
example: 212957153
startedAt:
type: string
description: Date and time the span was started in the [ISO 8601 / RFC3339](https://tools.ietf.org/html/rfc3339) format.
format: date-time
example: 2019-11-22 09:00:00+00:00
status:
$ref: '#/components/schemas/TraceSpanStatus'
kind:
pattern: ^(CLIENT|SERVER|PRODUCER|CONSUMER|INTERNAL)$
type: string
description: 'Span kind describes the relationship between the Span, its parents, and its children in a Trace. Possible values: `CLIENT`, `SERVER`, `PRODUCER`, `CONSUMER`, `INTERNAL`.'
example: SERVER
x-pattern-message: Should be either `CLIENT`, `SERVER`, `PRODUCER`, `CONSUMER` or `INTERNAL`.
remoteService:
type: string
description: Name of the possible remote span's service.
example: external-service
remoteServiceColor:
type: string
description: Color hex code assigned to the remote service.
example: '#fa41c6'
remoteServiceType:
$ref: '#/components/schemas/ServiceType'
info:
$ref: '#/components/schemas/TraceSpanInfo'
numberOfLinks:
type: integer
description: Number of span links in this span.
format: int32
example: 2
TraceSpanCriticalPathContribution:
required:
- duration
- fraction
type: object
properties:
duration:
type: integer
description: Overall processing time in nanoseconds consumed by this span in the critical path of its trace (a sum of the duration times of this span's critical path segments).
format: int64
example: 12957153
fraction:
type: number
description: The total fraction (value between 0.0 and 1.0) of the trace duration time consumed by this span in the critical path of its trace.
format: double
example: 0.4
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
TraceMetricsResponse:
required:
- metrics
type: object
properties:
metrics:
type: array
description: List of trace metrics.
items:
$ref: '#/components/schemas/TraceMetricDetail'
CriticalPathServiceBreakdownResponse:
required:
- elements
- idleTime
type: object
properties:
elements:
type: array
description: List of elements representing the critical path service breakdown.
items:
$ref: '#/components/schemas/CriticalPathServiceBreakdownElementDetail'
idleTime:
type: integer
description: Overall time in nanoseconds when no particular operation was in progress.
format: int64
example: 60000000
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'
TraceMetricDetail:
required:
- metric
- type
type: object
properties:
metric:
type: string
description: Trace metric name. In trace queries it can be used in `MetricTracingFilter.metric`.
example: _duration
description:
type: string
description: Short description of the metric.
example: The duration of a trace in nanoseconds.
type:
type: string
description: 'The type the values of this field will have. Possible values: `DoubleTracingValue`, `IntegerTracingValue`.'
example: IntegerTracingValue
EventAttributeValue:
required:
- type
properties:
type:
pattern: ^(BooleanEventAttributeValue|StringEventAttributeValue|DoubleEventAttributeValue|IntegerEventAttributeValue|BooleanArrayEventAttributeValue|StringArrayEventAttributeValue|DoubleArrayEventAttributeValue|IntegerArrayEventAttributeValue)$
type: string
description: Type of the event attribute value.
example: BooleanAttributeValue
discriminator:
propertyName: type
TracingValue:
required:
- type
properties:
type:
type: string
description: Type of the value model.
discriminator:
propertyName: type
CriticalPathServiceBreakdownElementDetail:
allOf:
- $ref: '#/components/schemas/CriticalPathServiceBreakdownElementBase'
- required:
- longestSegmentDuration
- numSpans
type: object
properties:
numSpans:
type: integer
description: Number of spans that are part of this service.
format: int32
example: 12957153
longestSegmentDuration:
type: integer
description: Number of nanoseconds the longest span segment in the critical path lasted.
format: int64
example: 12957153
TraceSpansResponse:
required:
- spans
- totalCount
type: object
properties:
spanPage:
type: array
description: List of trace spans.
items:
$ref: '#/components/schemas/TraceSpan'
totalCount:
type: integer
description: Total count of spans for this trace.
format: int64
example: 1234
next:
type: string
description: Next continuation token.
example: dlFXd0lhSkxzRjAwYnpVZkMrRmlhYnF4cGtNMWdnVEI
TraceQueryResultResponse:
required:
- results
type: object
properties:
results:
type: array
description: List of traces matching the query.
items:
$ref: '#/components/schemas/TraceDetail'
next:
type: string
description: Next continuation token.
example: '10001'
TraceQueryRowStatus:
required:
- count
- rowId
- status
type: object
properties:
rowId:
type: string
description: A unique identifier of the query.
example: A
status:
pattern: ^(Processing|Finished|Error|Canceled)$
type: string
description: 'Status of the query. Possible values: `Processing`, `Finished`, `Error`, `Canceled`.'
example: Processing
x-pattern-message: Should be either `Processing`, `Finished`, `Error`, `Canceled`.
statusMessage:
type: string
description: Descriptive message of the status
example: Finished successfully
count:
minimum: 0
type: integer
description: Number of results matching the query
format: int64
example: 3215
TraceExistsResponse:
required:
- exists
type: object
properties:
exists:
type: boolean
description: Indicates whether the trace with the given trace id exists.
example: true
url:
type: string
description: A path to the trace view page in Sumo Logic UI.
example: '#/trace/00000000000120CB'
CriticalPathResponse:
required:
- segments
type: object
properties:
segments:
type: array
description: List of span segments from the critical path.
items:
$ref: '#/components/schemas/SpanPathSegment'
next:
type: string
description: Next continuation token.
example: Mi93V0ZqTTBzaW89
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