Query summarized event counts by project for your Organization. Also see https://docs.sentry.io/api/organizations/retrieve-event-counts-for-an-organization-v2/ for reference.
the sum(quantity)
field is bytes for attachments, and all others the 'event' count for those types of events.
sum(times_seen)
sums the number of times an event has been seen. For 'normal' event types, this will be equal to sum(quantity)
for now. For sessions, quantity will sum the total number of events seen in a session, while times_seen
will be the unique number of sessions. and for attachments, times_seen
will be the total number of attachments, while quantity will be the total sum of attachment bytes.
sum(quantity)
- sum(quantity)sum(times_seen)
- sum(times_seen)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.You must either provide a statsPeriod
, or a start
and end
.
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 as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with end
instead of statsPeriod
.
This defines the inclusive end of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with start
instead of statsPeriod
.
If filtering by attachments, you cannot filter by any other category due to quantity values becoming nonsensical (combining bytes and event counts).
If filtering by error
, it will automatically add default
and security
as we currently roll those two categories into error
for displaying.
error
- errortransaction
- transactionattachment
- attachmentreplays
- replaysprofiles
- profilesSee https://docs.sentry.io/product/stats/ for more information on outcome statuses.
accepted
- acceptedfiltered
- filteredrate_limited
- rate_limitedinvalid
- invalidabuse
- abuseclient_discard
- client_discardYou 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.