Log record format
The log file is a gzip-compressed JSON+L file with one JSON object per line that represents a single log record entry. Each entry has the following format:
Field | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Number of bytes in the request. |
||||||||||
|
Number of bytes in the response. |
||||||||||
|
Number of read operations consumed by this query. |
||||||||||
|
Number of write operations consumed by this query. |
||||||||||
|
Number of compute operations consumed by this query. |
||||||||||
|
Database path of this entry. Each path entry is a database name. The first entry is the top-level database, and each included entry to the right is a child database. Dashboard queries have an empty database value. |
||||||||||
|
Full request body with Personal Identifiable Data removed. Used to associate the log entry with a query to help debug and understand traffic. |
||||||||||
|
Query processing time, in milliseconds. |
||||||||||
|
An array of ops types that were limited or approaching rate limits:
Example: |
||||||||||
|
Query Region Group identifier. |
||||||||||
|
HTTP request headers of this entry. |
||||||||||
|
HTTP request method of this entry. |
||||||||||
|
Query HTTP response code:
|
||||||||||
|
List of tags included with the query. Empty |
||||||||||
|
Query W3C-compliant traceparent identifier. If you supplied an identifier and the logs don’t include the identifier, you might have supplied an invalid identifier. If you provided an invalid identifier, Fauna generates a valid identifier. |
||||||||||
|
Query processing timestamp in UTC. Example: |
||||||||||
|
Retry count. A value greater than zero indicates contention. |
Is this article helpful?
Tell Fauna how the article can be improved:
Visit Fauna's forums
or email docs@fauna.com
Thank you for your feedback!