-
Notifications
You must be signed in to change notification settings - Fork 9
Add reserved field names, clarify action if hitting field limits #370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! <3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good, some small suggestions/questions
| | Limit | | ||
| ---------------------------- | --------- | | ||
| Maximum event size | 1 MB | | ||
| Maximum events in a batch | 10,000 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we have a limit on the number of events in a batch?
Maybe also list maximum field size of 1 MB? It feels a bit tautological (because the event itself cannot be bigger), but it makes sense to mention in the case where we replace strings longer than this with <invalid string: too long>
reference/field-restrictions.mdx
Outdated
|
||
Axiom creates the following two fields automatically for a new dataset: | ||
|
||
- `_time` is the timestamp of the event. If the data you ingest doesn’t have a `_time` field, Axiom assigns the time of the data ingest to the events. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it makes sense to add a link here, to how users can control what field from their data goes into _time
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, good idea. How does this look? 216f64e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, looks good 👍
Co-authored-by: Mikkel Kamstrup Erlandsen <[email protected]>
Preview: https://axiom-mano-reserved-fields.mintlify.app/reference/field-restrictions#limits-on-ingested-data
Basis:
https://watchlyhq.slack.com/archives/C03832MLBJA/p1755690031802139
https://watchlyhq.slack.com/archives/C1NJU9Y6B/p1756116638577429?thread_ts=1755726109.359199&cid=C1NJU9Y6B