POST
route in the API. Every route supports a set of allowed, predefined usage events. In some cases, like S3, these usage event types are given by the API methods supported by the service. In other cases, such as open-ended compute services like EC2, these usage event types are defined by Dashdive rather than the cloud provider.
Currently, only one event can be sent per POST
request, but an analogous batch route for each endpoint will be added soon.
"2013-01-01T04:00:00Z"
). Dashdive will attempt to honor timezone annotations (e.g. +08:00
) if present.{ "unknown_foo": "bar" }
) are included, the event will still be accepted, and the unexpected fields are simply ignored. Note that the data in those fields is permanently lost. Unlike hard schema violations where a required field is missing or malformed, validated events with extraneous fields are not recorded in their raw form.null
can always be passed for optional fields.<8_char_readable_prefix>.<48_char_base64_payload>
. For example: EXMPLKEY.SGVsbG8gd29ybGQgZnJvbSBEYXNoZGl2ZSEgKGJhc2U2NCk=
.