| Tip of the day: Log files can use JSON logging. You can also send the JSON data to IRCOps on IRC. The JSON is machine readable and contains lots of details about every log event. |
JSON-RPC:Whowas Object
Jump to navigation
Jump to search
The Whowas object looks similar to the Client Object (including an User Object) but is different in the sense that many fields are omitted, and some fields only exist for whowas entries (event, logon_time, logoff_time).
| Detail level | Variable | Description | Example value |
|---|---|---|---|
| 0+ | name | The name of the client (nick name, server name, ..) | Syzop
|
| 0+ | event | Event that caused the WHOWAS entry to be added, one of: quit, nick-change or server-terminating
|
quit
|
| 0+ | logon_time | Date/time when the nickname logged on (since last NICK change, or if none then identical to connected_since) | 2022-05-23T11:02:06.000Z
|
| 0+ | logoff_time | Date/time when the nickname logged off (when the nick change or quit happened) | 2022-05-23T11:02:06.000Z
|
| 1+ | hostname | Resolved hostname (or IP) | xyz.example.org
|
| 1+ | ip | IP address of the user (empty for services) | 198.51.100.1
|
| 1+ | details | Detailed description of the client. The output depends on the type of client and what information we have. |
nick!user@host
|
| 2+ | connected_since | Date/time when the client connected | 2022-05-23T11:02:06.000Z
|
| 2+ | user.username | The user name / ident | ~xyz
|
| 2+ | user.realname | The real name / GECOS | IRC User
|
| 2+ | user.vhost | If the user is +x or +t this contains the vhost/cloakedhost
|
oper/netadmin.test.net
|
| 2+ | user.servername | The server to which the user is connected | irc.example.net
|
| 2+ | user.account | The account name, if the user is logged in to Services. | SomeAccount
|