Reports and logs
The marketplace overview, the search log, member activity, the admin audit trail, security events, the e-mail log, the automation log and how long each is kept.
The group Reports answers two questions: how is the marketplace doing, and what happened. The first is the Marketplace Overview and the Search Log. The second is the member activity log, the admin audit trail, the security events, the e-mail log and the automation log. This chapter explains each page, its filters and what each line means.
1. Which right opens which page
| Page | Right needed |
|---|---|
| Marketplace Overview, Search Log & Trends | View reports |
| Member Activity, Admin Audit Trail, E-mail Log | View logs |
| Security Events | Security: bans, sessions, events |
| Automation Log | System, licence, API keys |
2. Reports → Marketplace Overview
A picture of the marketplace for a date range. At the top, From and To dates with a Show button and shortcuts for 7 days, 30 days (the default) and 90 days. The range cannot be longer than 366 days.
The eight tiles:
| Tile | Meaning |
|---|---|
| Members (all time) | Every member, staff included, not closed. |
| New members in this period | Sign-ups in the range. |
| Active listings | Live now. |
| Waiting for approval | Pending listings; orange when above zero. |
| Listings added in this period | Created in the range, whatever their status now. |
| Listing views in this period | Counted views (one per visitor per listing per 24 hours; the seller's own views and search-engine robots are not counted). |
| Inquiries in this period | New conversations started. |
| Sales in this period | The number and the total value, converted to the default currency. |
Below the tiles:
- Two bar charts, Listing views per day and Inquiries per day, for up to the last 60 days of the range. Hover a bar for the exact number.
- Members by status, Members by type and Listings by status as bars. Each bar links to the matching filtered list.
- Listings by type, the Top 10 extensions and the Top 10 categories among active listings. The last two link to the Domains list filtered by that extension or category.
- Sales in this period: the ten newest sales with domain, date, venue and price.
- Top sellers: sellers with a public profile, with their active listings and total sales.
Use this page for the monthly look at how supply (listings), demand (views, inquiries) and sales move together.
3. Reports → Search Log & Trends
Every search on the site is logged with its filters, the number of results, the member (if signed in) and the IP address. This page turns the log into ideas.
- The tabs Last 7 days, Last 30 days, Last 90 days and Last 180 days set the range for the two tables on top.
- Trending searches: what people searched for that found domains, with the number of times.
- Searches with no result: names and words people want and cannot find. This is your shopping list for recruiting sellers: contact sellers who might own such names, or publish a blog post on the topic.
- Search log, the raw list with filters Search text, Member (id, username or e-mail), Results (Any, Found something, Found nothing), From and To. Each row shows when, the text (or (filters only)), the filters used, the result count (a red 0 for nothing), the member and the IP address. A click on the text repeats the search on the site in a new tab.
Search rows are kept for 180 days.
4. Reports → Member Activity
What members did, one line per action: when, who, the action, a detail, a link to the record and the IP address. Filters: Member (id, username or e-mail), Action (a list of the actions that exist, for example register, email_verified, listing_created, watch, message, kyc_submitted, api_key_created, account_closed, listing_import), Record (the kind of record it points to: domain, conversation, kyc, ticket and so on), Detail contains, From and To. The same lines show on the Activity tab of one user.
Use it to answer "what did this member do before the problem?". It does not record page views.
5. Reports → Admin Audit Trail
Every staff action with the record before and after. Nothing a staff member does in the admin area changes data without a line here: settings saved, roles edited, listings approved, accounts suspended, KYC documents viewed, backups made, licence checks, imports.
| Column | Meaning |
|---|---|
| When | Date and time. |
| Staff | Who did it (a link to their record), or system. |
| Action | A short code such as listing_approve, user_suspend, settings_save, page_edit, ticket_reply. |
| Record | The kind and number of the record it touched, linked to the page when there is one. |
| Note | Free text (a reason, a changed tab) and, behind Show before and after, the data as it was and as it is now. |
| IP | The staff member's address. |
Filters: Staff member, Action contains (for example page_edit), Record type, Text (searches the note and the data) and the date range. Secrets such as passwords and keys are never written to the trail; changed settings that hold a secret show (set) and (changed) only.
The trail is your evidence in a dispute between staff, and your answer to "who changed this setting?". It is not deleted by the housekeeping job.
6. Reports → Security Events
Things worth a second look, newest and unseen first. Each has a Kind, a Severity (info, notice or warning), the member, a detail text and the IP address.
| Kind | Severity | Raised when |
|---|---|---|
failed_login | info | A wrong password for an existing account. |
brute_force_ban | warning | An address was banned after too many failed sign-ins. |
new_device | notice | An account was used from a device not seen before. |
recovery_code_used | notice | A two-factor recovery code was used to sign in. |
password_changed | notice | A password was changed. |
email_changed, failed_email_change | notice, info | A member changed the e-mail address, or typed a wrong password trying. |
twofa_enabled, twofa_codes, twofa_disabled | notice, notice, warning | Two-factor was switched on, recovery codes were remade, or it was switched off by the member. |
twofa_reset_by_admin | warning | Staff switched off a member's two-factor. |
spam_blocked | notice | An inquiry was refused by the spam filter. |
ownership_change | warning | A verified listing lost its verification or the owner changed. |
account_closed, failed_close | notice, info | A member closed the account, or typed a wrong password asking to. |
Filters: Kind, Severity, Member, State (All, Not seen yet, Seen), and dates. Tick rows and use the mark-seen button, or Mark all N as seen. The Dashboard shows the unseen ones in its Security events widget.
A run of failed_login from one address, a brute_force_ban, or a new_device followed by password_changed and email_changed on a seller account are the patterns to watch.
7. Reports → E-mail Log
Every mail the script tried to send, with its result. This is the first place to look when "the mail did not arrive".
- The list shows when, to, subject, template, and the status (Sent in green, Failed in red; hover for the error). Above the list a line tells how many messages failed, with a link to show them.
- Filters: To (an address), Subject, Template (the code of the template), Status (Any, Sent, Failed), From and To date.
- Open a message to see the body as the member got it, the status and error, the time, the address, Cc, the template and the member. Send this message again (needs the Mail settings and templates right) tries once more to the same address.
Sent means the mail server accepted it, not that the inbox received it. If a mail is Sent but never arrives, check the spam folder, then SPF and DKIM for your sending domain. See Troubleshooting. Rows are kept for 180 days.
8. Reports → Automation Log
What the cron job did. Four tiles: when the cron last ran (it should run every 5 minutes), jobs waiting, jobs failed, jobs done in 24 hours.
- Last run of each job (table: job, last run, result, seconds). The jobs are
heartbeat,queue,listing_expiry,search_alerts,pending_verifications,verify_recheck,registry_refresh,counters,currency_rates,sitemap,tickets,housekeeping,licence,update_check,pluginsandplugins_daily. - Failed jobs (queue entries that gave up after several tries): Retry and Delete per job, Retry all and Delete all. A queue job is one mail to send, one DNS check or one registry refresh.
- The log, with filters Job and Result (All, Worked, Failed): when, job, result, seconds and the message.
A job that fails shows the error in the message column and the same line goes to data/logs/cron.log. Rows are kept for 60 days.
9. How long things are kept
The daily housekeeping job removes old rows so the database does not grow for ever.
| Kept | For |
|---|---|
| Sign-in attempts (Login History) | 90 days |
| Search log | 180 days |
| Seen notifications | 90 days |
| Sessions not used | 30 days |
| Verification tokens, after they expire | 7 days |
| Expired IP bans | 1 day |
| E-mail log | 180 days |
| Automation log | 60 days |
| API log | 60 days |
| Finished queue jobs | 7 days |
Temporary files in data/tmp | 1 day |
| Member activity, admin audit trail, security events | Not removed |
If your privacy policy promises shorter times for the logs that stay, delete old rows from the database by hand or ask support for a custom job.