Retrieves discover (also known as events) data for a given organization.
Eventsv2 Deprecation Note: Users who may be using the eventsv2
endpoint should update their requests to the events
endpoint outline in this document.
The eventsv2
endpoint is not a public endpoint and has no guaranteed availability. If you are not making any API calls to eventsv2
, you can safely ignore this.
Changes between eventsv2
and events
include:
field
param exactly.meta
object in the response now shows types in the nested field
object.Aside from the url change, there are no changes to the request payload itself.
Note: This endpoint is intended to get a table of results, and is not for doing a full export of data sent to Sentry.
The field
query parameter determines what fields will be selected in the data
and meta
keys of the endpoint response.
data
key contains a list of results row by row that match the query
mademeta
key contains information about the response, including the unit or type of the fields requestedThe fields, functions, or equations to request for the query. At most 20 fields can be selected per request. Each field can be one of the following types:
field=transaction
tag[]
formatting to avoid ambiguity with any fields
field=tag[isEnterprise]
function_name(parameters,...)
. See possible functions in the query builder documentation.
field=count_if(transaction.duration,greater,300)
equation|
. Read more about equations here.
field=equation|count_if(transaction.duration,greater,300) / count() * 100
2001-12-14T12:34:56.7890
.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
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.
Filters results by using query syntax.
example: query=(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)
field
list, excluding equations.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, 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.