General > Developers Corner

LuaLog

<< < (2/2)

Buzzkill:

--- Quote from: MrPresident on March 07, 2015, 11:48:27 AM ---You CAN use them if you want, because they're simply ignored in lua.. but if you are going to use them at least be consistent.

--- End quote ---

I know, I know.  :)  Too many languages and too much muscle memory.  My Java fingers still want to put a semicolon at the end of everything.


--- Quote from: Bite That Apple on March 06, 2015, 07:44:33 PM ---Right now it's simply a work in progress.  I had thrown it out there simply as some semi-interesting log parsing logic for anyone that might ever want to dissect it, but then I changed things up and actually asked a question (the Lua error hook).

--- End quote ---
Ultimately what I'm working towards is a db-based, multi-server logging system that can be accessed via the web to produce chat/error/event logs by day. The main point I'm waffling on is whether the parsing should be done completely outside of GMod (as I'm currently doing, which gives me cleaner access to errors as well as the ability to write to a centralized db), or if I should create wrapper hooks for everything within GMod and write the logs that way, which will unfortunately prevent me from seeing Lua errors and would make the centralized logging tricky if not impossible.


--- Quote from: JamminR on March 06, 2015, 10:11:55 PM ---I'm guessing - yes.
One would have to find and see if the original lua error system in Gmod was done in lua (or, sadly in this case, it might be the lua compiler itself)
I've not researched how to look at all of Gmod lua code in quite some years. It used to be quite plainly visible.

--- End quote ---

Thanks.  Yes, I'm thinking it's the Lua compiler itself, given how pure the stack dump looks.

Bite That Apple:

--- Quote from: Buzzkill-THABB on March 09, 2015, 06:35:43 AM ---or if I should create wrapper hooks for everything within GMod and write the logs that way, which will unfortunately prevent me from seeing Lua errors and would make the centralized logging tricky if not impossible.

--- End quote ---

I like your first idea, about making it outside of Garry's Mod, what a fantastic; and unique idea. As for your second idea, I'm not entirely sure if you are able to do that. I don't know if that's even possible, but you sound like you know more than I do, so good luck towards your project.

It would be interesting to see this project on release to everyone, or at least on codefodder (i think that's what it is called.)

Buzzkill:
I've been noodling this idea a little more, and keep coming back to the notion of multi-server (which was the original driver) *AND* multi-addon, which is rapidly becoming another hot-button issue for me.  I now have multiple addons on multiple servers that all produce interesting artifacts in terms of event information (ie, chat logs, Cake Anticheat flags, raw lua errors, etc).  It's becoming information overload and I'm losing insight.

So, in the spirit of BHAGS (big, hairy audacious goals), I'm rebranding LuaLog as the Grand Unifying Tracking System (GUTS), at least for now, with the goal of building a flexible programmatic interface so that it can hook into different systems (actual Gmod hooks, file patterns such as console and CAC logs, etc, etc).

Just an FYI... and my Cortez moment (ie, by announcing this in a somewhat public way, I'm less likely to cast it off when something shinier comes down the road).

:)

JamminR:
*drool*
SQUIRREL
* JamminR wipes corner of lip.

Buzzkill:
This finally has a repo and I've published my current code.  It's currently strictly ULX logs, strictly Sqlite and very, very beta... but stay tuned.


https://github.com/THABBuzzkill/lualog

Navigation

[0] Message Index

[*] Previous page

Go to full version