View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006035 | unreal | ircd | public | 2021-12-23 14:10 | 2021-12-23 16:21 |
| Reporter | armyn | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Product Version | 6.0.0 | ||||
| Summary | 0006035: Enlarge the JSON of TKL_ADD to have all of a single result | ||||
| Description | There would be no way to put the two results together on one JSON? : "timestamp": "2021-12-23T12:46:22.201Z", "level": "info", "subsystem": "tkl", "event_id": "TKL_ADD", "log_source": "irc.domain.com", "msg": "G-Line added: '*@lfbn-ip.abo.wanadoo.fr' [reason: test test] [by: Admintest!Admintest@coder/b3Az] [expires: Thu Dec 23 12:46:27 2021 GMT]", "tkl": { "type": "gline", "type_string": "G-Line", "set_by": "Admintest!Admintest@coder/b3Az", "set_at": "2021-12-23T12:46:22.000Z", "expire_at": "2021-12-23T12:46:27.000Z", "set_at_string": "Thu Dec 23 12:46:22 2021 GMT", "expire_at_string": "Thu Dec 23 12:46:27 2021 GMT", "set_at_delta": 0, "name": "*@lfbn-ip.abo.wanadoo.fr", "reason": "test test" } and (it comes from the exiting client): "client": { "name": "Lyre", "id": "001KVUXOB", "hostname": "lfbn-ip.abo.wanadoo.fr", "ip": "90.109_ip", "details": "[email protected]", "connected_since": "2021-12-23T11:45:49.000Z", "user": { "username": "o-dcs-fr849b24b-1", "realname": "17/F/00/FR", "servername": "irc.domain.com", "reputation": 113, "security-groups": ["known-users", "webirc-users", "tls-and-known-users", "tls-users"], "modes": "ipwxzI" } }, The best is to have the hostname + the ip + username + time + time_expire of the client in the json of the tkl_add at least and possibly the realname, It's to avoid records in two different json in sql, it's difficult, doing it all at once is better In each of the two json (tkl_add and client exiting) there is everything I need, but taken individually some info is still missing | ||||
| 3rd party modules | |||||
|
|
The TKL_ADD event is about a TKL (a gline in this case) being added. At that point it does not know yet which users are affected. It could be 0 users, 1 user or 1000 users, or anything in between or more. The LOCAL_CLIENT_DISCONNECT event (and similar) indeed deals with a particular client, so that's why you see details there. I'm afraid I don't see a way for them to be merged. Due to: 1) code paths.. things taking place at different places, 2) as a principe since they technically are unrelated, 3) the amount of users that could be affected, 4) space / cutoff issues (4k/8k limit) |