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.
Because of technical limitations, this endpoint returns "
"at most 10000 data points. For example, if you select a 90 day window grouped by releases, "
"you will see at most floor(10k / (90 + 1)) = 109
releases. To get more results, reduce the "
"statsPeriod
."
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]("
"https://github.com/getsentry/sentry/discussions/42716) 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)
2001-12-14T12:34:56.7890
.2001-12-14T12:34:56.7890
.The period of time for the query, will override the start & end parameters, a number followed by one of:
d
for daysh
for hoursm
for minutess
for secondsw
for weeksFor example 24h
, to mean query data starting from 24 hours ago to now.
The IDs of projects to filter by. -1
means all available projects.
For example the following are valid parameters:
/?project=1234&project=56789
/?project=-1
Resolution of the time series, given in the same format as statsPeriod
.
The default and
the minimum interval is 1h
.
The list of properties to group by.
The available groupBy conditions are project
,
release
, environment
and session.status
.
field
. Use -
for descending order, for example -sum(session)
0
to exclude totals from the response. The default is 1
0
to exclude series from the response. The default is 1
Filters results by using query syntax.
example: query=(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)
Specify how the response should be mapped to the table output. The following formats are available:
Structured Table: Returns a parsed table with data split into rows and columns.
Raw Response: Returns the raw response in a single row with the following columns:
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.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.