Returns a time series of release health session statistics for projects bound to an organization.
The interval and date range are subject to certain restrictions and rounding rules.
The date range is rounded to align with the interval, and is rounded to at least one hour. The interval can at most be one day and at least one hour currently. It has to cleanly divide one day, for rounding reasons.
Apart from the query parameters listed below, this endpoint also supports the usual pagination parameters.
The ID of the projects to filter by.
Use -1
to include all accessible projects.
The list of fields to query.
The available fields are
sum(session)
count_unique(user)
avg
, p50
, p75
, p90
, p95
, p99
, max
applied to session.duration
. For example, p99(session.duration)
. Session duration is no longer being recorded as of on Jan 12, 2023. Returned data may be incomplete.crash_rate
, crash_free_rate
applied to user
or session
. For example, crash_free_rate(user)
The list of properties to group by.
The available groupBy conditions are project
, release
, environment
and session.status
.
Grouping by session.status
does not work when crash_rate
or crash_free_rate
are queried.
An optional field to order by, which must be one of the fields provided in field
. Use -
for descending order, for example -sum(session)
.
This alters the order of the groups
returned, so it only makes sense in combination with groupBy
.
Ordering by more than one field is currently not supported.
A free-form query that is applied as a filter.
An example query could be release:"1.1.0" or release:"1.2.0"
.
This defines the range of the time series, relative to now.
The range is given in a "<number><unit>"
format.
For example 1d
for a one day range. Possible units are m
for minutes, h
for hours, d
for days and w
for weeks.
It defaults to 90d
.
This is the resolution of the time series, given in the same format as statsPeriod
.
The default resolution is 1h
and the minimum resolution is currently restricted to 1h
as well.
Intervals larger than 1d
are not supported, and the interval has to cleanly divide one day.
This defines the start of the time series range, in the same format as the interval
, relative to now.
This defines the end of the time series range, in the same format as the interval
, relative to now.
The time slices of the timeseries data given in the groups[].series
field.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension Sentry Nodes from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.