Minor changes and enhancements
- [New] When performing create, update, and delete requests through Sumo Logic APIs, the API accessID is now included within the operator field of your related Audit Event Index messages.
This is an archive of 2022 Developer Release Notes. To view the Developer Release Notes archive, click here.
Welcome to the Sumo Logic Developer Release Notes on our new docs site! We're now open source and encourage you to contribute. We welcome all contributions, from minor typo fixes to brand new docs. Your expertise and sharing can help fellow users learn and expand their knowledge of Sumo Logic.
This is an archive of 2021 Developer Release Notes. To view the Developer Release Notes archive, click here.
New - The Metrics Query API allows you to execute queries on various metrics and retrieve multiple time-series (data-points) over time from HTTP endpoints.
New - The Policies Management API allows you to control the security and share settings of your organization from HTTP endpoints.
New - The Field Extraction Rule (FER) Management API allows you to manage FERs from HTTP endpoints.
This is an archive of 2020 Developer Release Notes. To view the Developer Release Notes archive, click here.
New - Installation Tokens provide Installed Collectors a great alternative to Access Keys. They do not expire and can only be used to register Installed Collectors. You can embed your Installation Tokens in installation scripts confident they can't be used to make API requests if compromised.
New - The Tokens Management API is available to manage Installation Tokens from HTTP endpoints.
The Access Keys, SAML, and Service Whitelist APIs are in open beta.
For links to API documentation see APIs in Beta.
The Lookup Table Management API is now in closed beta. You can use the API to view and manage lookup tables. A lookup table is a table of data hosted on Sumo Logic that you can use to enrich the log and event data received by Sumo Logic. For more information, see APIs in Beta.
This is an archive of 2019 Developer Release Notes. To view the Developer Release Notes archive, click here.
The App Installation API is now in open beta. You can use the API to view and install Sumo Logic applications. For more information, see APIs in Beta.
Update - Steps for generating clients now use OpenAPI Generator instead of Swagger Codegen. Using Swagger Codegen will generate a backward incompatible client. For more details, see https://github.com/swagger-api/swagger-codegen/issues/9103
Update - The Collector Management API can return Collectors by name and manage offline Collectors with the
Beta endpoints will be deprecated effective August 1, 2019. If you have any questions reach out to us at firstname.lastname@example.org.
Update - Added hostname as a Collector environment variable in our Docker image.
Update - The security services of our API framework has been upgraded. API requests with multiple forward slashes (
//) will receive a "500 Internal Server Error" response.
New - User and Role APIs allow administrators to programmatically create and manage users and roles, making it easy to integrate Sumo into existing onboarding/offboarding business workflows.
This is an archive of 2018 Developer Release Notes. To view the Developer Release Notes archive, click here.
New - As part of our new API-centric development approach, we have several Sumo Logic APIs now available. Contact your sales rep to sign up to be one of our Beta Customers for the following APIs:
And the following APIs are coming soon:
New - Receipt time is now available for scheduled searches, share links for searches, pinned searches, and Search Job API queries. To support receipt time, the Search Job API has a new parameter,byReceiptTime.
Techniques that manage load, like rate limiting and throttling, help keep the Sumo platform reliable and stable. Towards that end, a new Search Job API throttling limit was introduced today. Until now, search jobs were subject only to the global rate limit: each user is limited to four API requests/second. Now, to improve reliability Sumo is limiting the number of active search jobs for a given account to 200. To manage the number of active search jobs, you can manually clear completed searches.
For more information, see Search Job API throttling.