The Span Analytics API allows you to browse spans collected in the system. You can execute queries to find individual spans matching provided search criteria as well as run aggregated span queries and retrieve their results. For more information, see Spans.
Endpoints for API access
Sumo Logic has deployments that are assigned depending on the geographic location and the date an account is created. For API access, you must manually direct your API client to the correct Sumo Logic API URL.
See Sumo Logic Endpoints for the list of the URLs.
HTTP 301 Moved error suggests that the wrong endpoint was specified.
While the span analytics query is running you need to request the query status based on the query ID. The API keeps the query alive by either polling for status or gathering results. If the search job is not kept alive by API requests, it is canceled after fifteen minutes. When a query is canceled after fifteen minutes of inactivity, you will get a 404 status.
The APIs return operation failures with a description and error code, including the following generic errors that apply to all APIs:
|The requested resource SHOULD be accessed through returned URI in Location Header.
|Credential could not be verified.
|This operation is not allowed for your account type.
|Requested resource could not be found.
|Unsupported method for URL.
|Invalid content type.
|The API request rate is higher than 4 request per second.
|Internal server error.
|Service is currently unavailable.
Documentation for OpenAPI built APIs is hosted on each deployment. Sumo Logic has several deployments that are assigned depending on the geographic location and the date an account is created. See how to determine which endpoint to use if you are unsure.
Select the documentation link for your deployment: