Skip to content
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.

Stop using SQLite for logging server events like IC and OOC #190

Open
Crystalwarrior opened this issue Aug 16, 2021 · 6 comments
Open

Stop using SQLite for logging server events like IC and OOC #190

Crystalwarrior opened this issue Aug 16, 2021 · 6 comments
Assignees

Comments

@Crystalwarrior
Copy link
Contributor

Crystalwarrior commented Aug 16, 2021

SQLite should only be used for handling bans, etc. Handling the area logs is only leading it to grow in size, and it's disgustingly easy to corrupt the database when trying to view the logs. It takes 30 seconds to run any given schema on especially large databases.

The solution is to bring back text logging for anything that's not benefiting from SQLite-specific features, such as bans.

also see Crystalwarrior/KFO-Server#11, same issue since KFO is a fork of tsu3. Planning to attempt some solutions on my end at some point.

@Crystalwarrior
Copy link
Contributor Author

@oldmud0 oldmud0 self-assigned this Aug 21, 2021
@oldmud0
Copy link
Member

oldmud0 commented Aug 21, 2021

working on it

@Crystalwarrior
Copy link
Contributor Author

working on it

Oh yeah since you discontinued tsu3 wanna help kfo server :)

@oldmud0
Copy link
Member

oldmud0 commented Aug 22, 2021

Yeah I'm changing my changes to do a PR on kfo-server. It's a slightly different codebase.

I'm planning to support two different formats:

  1. Standard logging format that is easy to read.
2021-08-20 22:50:02.055 [BAS] Lana (ipid: 4484, ooc_name: web44, showname: None) shouted: Hey you, what's up?
2021-08-20 22:50:02.055 [BAS] Lana (ipid: 4484, ooc_name: web44, showname: None) said in OOC: ((case??))
2021-08-20 22:50:02.055 [BAS] Lana (ipid: 4484, ooc_name: web44, showname: None) said: ((case??))
2021-08-20 22:50:02.055 [BAS] Lana (ipid: 4484, ooc_name: web44, showname: None) disconnected from the server.
  1. Debug-friendly format that is extremely parseable and searchable (especially with tools like Splunk that are specialized for aggregating terabytes upon terabytes of log files), but still readable.
2021-08-20 22:50:02.055 area=BAS ipid=4484 uid=32 cid=5 event=disconnect
2021-08-20 22:50:02.055 area=BAS ipid=4484 uid=32 cid=5 event=chat char_name="Lana" ooc_name="web44" showname="" message="Yo what's up"
2021-08-20 22:50:02.055 area=BAS ipid=4484 event=connect success=false

I don't think there is a substantial demand for the latter, so I might just keep that change specific to my server.

@Crystalwarrior
Copy link
Contributor Author

working on it

any progress on this

@oldmud0
Copy link
Member

oldmud0 commented Feb 4, 2022

🪦

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants