Open bbugh opened 3 months ago
Thanks for reporting! I am transferring this issue to our documentation repository
Assigning to @getsentry/support for routing ⏲️
hello, any update on this?
Routing to @getsentry/product-owners-sdks-web-backend for triage ⏲️
Apologies and thanks for your patience, it seems this issue fell through the cracks!
The file that you pass to send-event
needs to be a valid JSON file. The file can contain any of the attributes documented here.
We will update the send-events
docs page to include this information
👋 This is a documentation issue, which you don't have a template for. Apologies if this isn't in an optimal format.
Issue
In this section of the documentation
https://docs.sentry.io/product/cli/send-event/#stored-events
It says
However, there is no link or references to what a "stored JSON representation" is.
By digging into the source code and finding a test fixture I was able to find an example representation.
However, looking through the docs (and some Sentry experience) I see that this doesn't represent any data format that I know of. It kind of looks like what you'd send with a breadcrumb, but breadcrumbs are
type
,category
,message
,level
,timestamp
anddata
, but this fixture has different keys:Exploring further, I'm guessing from this integration test that the keys might be the same as the command line arguments that can be passed in to
send-event
, and usingsentry-cli send-event --help
shows many of the same flags, but there's a difference thatevent.json
usesenvironment
key, but the command line flag isenv
.That implies to me that one of those is a typo, or that this still isn't the correct JSON schema.
Expected Result
There is more information about what the "JSON representation of an event" means.
Thank you for reading!