/tg/Station 13

So a few days ago, I setup public logs for runtime logs, and posted in the coder forum with info on how to access them.

Today, I bring the full thing, public logs!

Filtered/censored info:

• Any line that doesn't start with a timestamp (because i'm too lazy to make the parser work with them. this is mainly debug lines/info about the game banners asking for the server status, and tcom script uploads) These are filed under "misc" when censored.
• Any admin communication (asay/apm/ahelp)
• Watchlist and notes adding/editing/removing
• Ban reasons
• Anything that matches the format of 0-255.0-255.0-255.1-255 (ips)
• cids and ips from connection log lines.
• Any line that starts with ADMIN: and is followed by <a (because these are bugged and harder to parse, newer logs don't have this issue, but the older ones do.)
• Log entries about invalid connection data (these can contain cid/ip info in a hard to predict way)

Server time zone is ESTGMT.
Log files for the current day are excluded, and you have to wait until they roll over about an hour after the first round to start after midnight EST. Log files are uploaded within 5 minutes of the round ending.

https://tgstation13.org/parsed-logs/

You may request json based directory indexes using "?index_format=json".

New rules regarding the use of public logs in ban appeals, ban requests (if ever re-opened) and admin complaints:

• The content of line must not be modified in any way.
  • This does not apply to adding context (as long as its clear that its added and not part of the original log)
  • Likewise, you are allowed to add formatting or emphasis as long as it does not appear deceptive
• Any omissions of in between lines must be clearly marked in-line to the logs along with a brief description giving a rough amount of the lines removed, what they contained, and why they were removed
  • -snip-(500 lines of the clown slipping the hos in the other room removed for being irrelevant)
• You must link to the log file you got the logs from to make it easier to validate the context
• Air on the side of good faith, Its better to include too many context lines then not enough lines context lines
• Expect onlookers to assume bad faith. If you omit details that are later deemed to be important people will assume you did it intentionally. This means doing due diligence when reviewing the logs for related or relevant bits.

Very cool, I'll be interested in seeing what this does for OOC conduct and whatnot.

Very cool, Sorry if this isn't the place for it, but I dunno how bad the storage on such a thing is and might become moving forward, But you might save space by additionally filtering polly action, monkey actions, etc etc examples here

I'm guessing it would be a few hundred megabytes a month at most, which is probably less than 10 gig a year. Space is cheap and if /tg/station13 is still around when it becomes a problem it probably wouldn't be too much to raise the patreon by however much.

It would make shit easier to read though.

Regular expressions are pretty interesting things.

Whilst I was searching through the logs to see how often I've played lately (to see if I've been more active than HG), I saw someone talking about me in OOC.
Having notepad++ installed and knowing it was a really powerful tool, that I had zero fucking clue at how to use, I decided to spend the last hour or so dicking through google trying to arse my way around RegEx to see if I could find if other people talk about me when I'm not there.

Eventually I came up with this RegEx: Which searches for log lines of OOC chats, and then filters them to find lines that contain people talking about me but weren't started by me.

If you want to know what the syntax means, well... you can look it up your fucking selves.
If you just want to know what people are saying about you when you're not there, feel free to modify this for your own purposes.



Turns out people do talk about me.
Mostly sadbutt still blaming his own failures on me; bgobandit's abandonment issues; and people that take space law far far too seriously

You can replace those '.*?' with just '.*', remove that [Mm] and just check the case insensitive checkbox, and get rid of the ^ anchor since I'm pretty sure Notepad++'s flavor doesn't match . with [\r\n] anyway. But now I'm just nitpicking.

I don't think I'll be using the logs much, unless it's for a FNR thread or something. Way too much second-hand embarrasment.

The ^carot is needed, otherwise the search result returns the entire document instead of the line.

Caret*

any particular reason why these are kill

There's a few bugs with the log parsing currently, it'll be back.

It's broken again.

No 2016 logs?

Hello, are logs ever returning?

IIRC They're disabled due to a byond issue, I'll try and find where MSO mentions it.

I think someone said something about a security breach with them? Or was that wrong.

They are currently disabled due to a security issue. It is not a BYOND bug, merely unfortunate behavior. Regular and attack logs may return, but runtime logs are permanently disabled.

Are logs still disabled?
I noticed theres some logs past Jan but none since the end of feb - so are they updating or not?

oh ya, i never did re-enable auto update on the web server.

one second, let me fix that.

Public logs are still down for about 3 weeks now, do you have an ETA on when it'll be back up?

Logs need to be updated constantly, how else will I know what dead chat says about me when I release the geese?!

Finally got around to fixing and redoing the upload system.

Thanks MSO!

The config is now public

https://tgstation13.org/parsed-logs/basil/config/
https://tgstation13.org/parsed-logs/sybil/config/

Because the end of days scenario where everybody nitpicked over logs to get back at who ever rekt'ed them never even happened, game logs for a round will now go public within 5 minutes of the round ending, rather than waiting for the next day to roll the logs over.

MrStonedOne wrote:Because the end of days scenario where everybody nitpicked over logs to get back at who ever rekt'ed them never even happened, game logs for a round will now go public within 5 minutes of the round ending, rather than waiting for the next day to roll the logs over.

I thought part of that was because the log files all dump by the day and not by round, that's cool though.

New rules regarding the use of public logs in ban appeals, ban requests (if ever re-opened) and admin complaints:

• The content of line must not be modified in any way.
  • This does not apply to adding context (as long as its clear that its added and not part of the original log)
  • Likewise, you are allowed to add formatting or emphasis as long as it does not appear deceptive
• Any omissions of in between lines must be clearly marked in-line to the logs along with a brief description giving a rough amount of the lines removed, what they contained, and why they were removed
  • -snip-(500 lines of the clown slipping the hos in the other room removed for being irrelevant)
• You must link to the log file you got the logs from to make it easier to validate the context
• Air on the side of good faith, Its better to include too many context lines then not enough lines context lines
• Expect onlookers to assume bad faith. If you omit details that are later deemed to be important people will assume you did it intentionally. This means doing due diligence when reviewing the logs for related or relevant bits.

Public logs have been updated for the new round based system.

To come: archives for days/months and admin interface for getting unfiltered logs.

I had a PR merged to add Telecomms logs to these into a new file a few weeks back (https://github.com/tgstation/tgstation/pull/39276), as well one on the tgstation13.org repo to add the new file to the zips (https://github.com/tgstation/tgstation13.org/pull/47), but it's not showing up on the public logs even though it's saving fine on my local testing server.

I'm not sure if I forgot to add the file somewhere else or if some config isn't up to date, any ideas?

It seems like photos are trimmed from the public logs. Can they make a return, or are they deleted anyway?