Help: Ledger
Export and verify the ledger
An export is a file of your ledger's events that you keep outside funwatcher. Every member of the account can download one. A copy you hold yourself is what lets you show later that the record has not been rewritten. See What the ledger is.
Download an export
- Open the Ledger and choose the account if you have more than one.
- To export part of the ledger, set "From" and "To" and select "Filter". Leave both empty to export everything.
- Select "Export JSON" or "Export CSV".
The file downloads with a name that starts with "ledger-" and ends in .json or .csv.
- The export follows the "From" and "To" dates only. The "Event type" and "Agent" filters do not apply to it: every event in the date range is included.
- Events are in sequence order, oldest first.
What is in the file
| Field | Meaning |
|---|---|
seq | The event's sequence number. |
event_type | The type of event. |
request_id | The request the event belongs to, if any. |
actor_type, actor_id | Who caused the event. |
payload_hash | The hash of the event's details. |
prev_hash | The hash of the event before this one. |
hash | This event's own hash. |
created_at | The time of the event. |
payload | The details recorded with the event. Empty in CSV, and null in JSON, when they were purged under the retention setting. |
The JSON file also has a header: account_id, since, until, exported_at, event_count, first_hash and last_hash. The CSV file has one row per event under a row of column names.
An export contains decrypted details of your agents' activity. Store it as carefully as the accounts it describes.
Check an export against a monthly statement
A statement prints the hash of the first and the last event of its month. An export of the same month must show the same two hashes.
- Open the statement for the month. See Monthly statements.
- On the Ledger page, set "From" to the first day of that month and "To" to its last day, and select "Filter".
- Select "Export JSON".
- Compare
first_hashin the file with the hash printed under "First event" on the statement. - Compare
last_hashin the file with the hash printed under "Last event". - Compare
event_countwith "Events this month".
If all three match, the month in the ledger today is the month the statement described. In a CSV export, compare the hash column of the first and the last row.
If they do not match, check the dates first: statement months run in UTC. If the dates are right, the stored history differs from the statement. Keep both files and contact the operator of your deployment.
Check the links inside an export
- Open the export.
- For each event after the first, compare its
prev_hashwith thehashof the event before it.
They are equal for every pair in an unaltered ledger. The prev_hash of the very first event of an account is a row of zeros.
What this check does not show
- It shows that the record is unchanged. It does not show that the agents did what they reported.
- It is only as strong as where you keep your copies. A statement or export kept only inside the same deployment does not protect against someone who controls that deployment.
Previous: Browse and filter the ledger
Next: Payload retention
All help pages
Inbox
- Read a request
- Approve, deny or edit a request
- Held actions
- Expired requests and history
- Request statuses
Rules
- How rules work
- The default rules
- Write a rule in plain English
- Build a rule with the form
- Reorder, enable and disable rules
- Suggested rules
- Set a default policy for an agent
- Export your rules
Teams
Ledger
- What the ledger is
- Browse and filter the ledger
- Export and verify the ledger
- Payload retention
- Monthly statements
Billing
Account and security
- Change your password
- Two-factor authentication and recovery codes
- Rotate or revoke an agent key
- How your data is protected
- Closing an account