Releases API - GET releases
Lists all available releases.
The request produces an application/json
payload.
GET | SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/releases |
Environment ActiveGateCluster ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/releases |
Authentication
To execute this request, you need an access token with releases.read
scope.
To learn how to obtain and use it, see Tokens and authentication.
Parameters
The start of the requested timeframe.
You can use one of the following formats:
- Timestamp in UTC milliseconds.
- Human-readable format of
2021-01-25T05:57:01.123+01:00
. If no time zone is specified, UTC is used. You can use a space character instead of theT
. Seconds and fractions of a second are optional. - Relative timeframe, back from now. The format is
now-NU/A
, whereN
is the amount of time,U
is the unit of time, andA
is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example,now-1y/w
is one year back, aligned by a week. You can also specify relative timeframe without an alignment:now-NU
. Supported time units for the relative timeframe are:m
: minutesh
: hoursd
: daysw
: weeksM
: monthsy
: years
If not set, the relative timeframe of two weeks is used (now-2w
).
The end of the requested timeframe.
You can use one of the following formats:
- Timestamp in UTC milliseconds.
- Human-readable format of
2021-01-25T05:57:01.123+01:00
. If no time zone is specified, UTC is used. You can use a space character instead of theT
. Seconds and fractions of a second are optional. - Relative timeframe, back from now. The format is
now-NU/A
, whereN
is the amount of time,U
is the unit of time, andA
is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example,now-1y/w
is one year back, aligned by a week. You can also specify relative timeframe without an alignment:now-NU
. Supported time units for the relative timeframe are:m
: minutesh
: hoursd
: daysw
: weeksM
: monthsy
: years
If not set, the current timestamp is used.
The cursor for the next page of results. You can find it in the nextPageKey field of the previous response.
The first page is always returned if you don't specify the nextPageKey query parameter.
When the nextPageKey is set to obtain subsequent pages, you must omit all other query parameters.
The amount of Releases in a single response payload.
The maximal allowed page size is 1000.
If not set, 100 is used.
Get your Releases (false
) or a set of demo Releases (true
).
Defines the scope of the query. Only Releases matching the provided criteria are included in the response.
You can add one or several of the criteria listed below.
- Management zone: type(PROCESS_GROUP_INSTANCE),mzName("ManagementZone-A"). Filters for all releases in the given management zone. The filter is case-sensitive.
- Monitoring state: monitoringState("Active") or monitoringState("Inactive"). You can specify only one monitoring state.
- Health state: healthState("HEALTHY") or healthState("UNHEALTHY"). You can specify only one health state.
- Security vulnerability: affectedBySecurityProblem("Detected") or affectedBySecurityProblem("Not detected"). You can specify only one security vulnerability state.
- Name: entityName("name"). Filters for all releases that contain the given value in their name. The filter is case-insensitive.
- Entity ID: entityId("id").
- Product: releasesProduct("product"). Filters for all releases that contain the given value in their product. The filter is case-insensitive.
- Stage: releasesStage("stage"). Filters for all releases that contain the given value in their stage. The filter is case-insensitive.
- Version: releasesVersion("version"). Filters for all releases that contain the given value in their version. The filter is case-insensitive.
To set several criteria, separate them with comma (,). Only results matching all criteria are included in the response. e.g., .../api/v2/releases?releasesSelector=name("Server"),monitoringState("Active"),healthState("HEALTHY"),releasesVersion("1.0.7").
The special characters ~ and " need to be escaped using a ~ (e.g. double quote search entityName("~"").
Specifies the field that is used for sorting the releases list. The field has a sign prefix (+/-) which corresponds to the sorting order ('+' for ascending and '-' for descending). If no sign prefix is set, then the default ascending sorting order will be applied. You can sort by the following properties:
- 'product': Product name
- 'name': Release name
- 'stage': Stage name
- 'version': Version
- 'instances': Instances
- 'traffic': Traffic
If not set, the ascending order sorting for name is applied.
Response
Response codes
Response body objects
The Releases
object
A list of releases.
The cursor for the next page of results. Has the value of null
on the last page.
Use it in the nextPageKey query parameter to obtain subsequent pages of the result.
The number of entries per page.
Number of releases with problems.
The total number of entries in the result.
The Release
object
Contains data related to a single release of a component. A Release is a combination of a component and a version. A Component can be any form of deployable that can be associated with a version. In the first draft, a Component is always a Service.
The tuple <name, product, stage, version> is always unique.
The entity has one or more problems
The entity has one or more security vulnerabilities
The entity name
The number of problems of the entity
The product name
The entity id of correlating release.
The related PGI is still running/monitored
The number of security vulnerabilities of the entity
Indicates that the security vulnerabilities feature is enabled
The stage name
The count of bytes per second of the entity
The identified release version
The ReleaseInstance
object
Contains data related to a single instance of a release. An instance is a Process Group Instance and has an optional build version.
The build version
The entity id of the instance.
List of event Ids of open problems
List of Security vulnerabilities Ids
The SoftwareTechs
object
Contains information about the used software technology.
The edition of the technology.
The type of the technology.
The verbatim type of the technology.
The version of the technology.
Response body JSON model
{"nextPageKey": "AQAAABQBAAAABQ==","pageSize": 1,"releases": [{"affectedByProblems": true,"affectedBySecurityVulnerabilities": true,"instances": ["PROCESS_GROUP_INSTANCE-49D94B90FB71C45B","PROCESS_GROUP_INSTANCE-7EA049157C82D1A5"],"name": "cluster","problemCount": 4,"product": "Sockshop","releaseEntityId": "PROCESS_GROUP-DFDBAC9CBF104253","running": true,"securityVulnerabilitiesCount": 4,"securityVulnerabilitiesEnabled": true,"softwareTechs": [{"edition": "OpenJDK","technology": "JAVA","verbatimType": "Java","version": "1.8.0_242"}],"stage": "staging","throughput": 923234,"version": "1.195.34.12341232423-012342"}],"releasesWithProblems": 1,"totalCount": 1}