Banned from trends.tf. Nothing I can do about logs.tf.

And just to answer my own question, the upload time gets updated any time the log is modified. Logs can be updated at any time.

It's been a while since the last update. I'm still working on the site, but recently a lot of that has gone into stuff behind-the-scenes.

• The whole site configuration got added to version control. I can now spin up a new server in around 30 minutes. I can also track configuration changes with the rest of the site. This has been particularly helpful for working with nginx.
  
• I switched to Digital Ocean from Azure, since my student discount ran out. I'm pretty happy with them. I may upgrade to a larger instance if I ever see an uptick in traffic. The database could really use more ram.
  
• I added tracing/error reporting using Sentry. This should help me address slow queries and determine if the changes I made are having the affect I wanted. It also has helped me quickly identify errors. I've pushed out several bug fixes recently using errors I found with Sentry.

In addition to the above, there are also some feature updates

• There is now a recent logs page where you can see all logs uploaded to the site.
  
• You can now filter by player. The search is for aliases like the search box, but it only shows their current name. I may try and fix this at some point.
  
• Weapons now use their in-game names. I'm using a semi-automated process for this, so let me know if you see any weird weapon names.
  
• The combined log limit has been increased to 10. This is primarily so that you can do combined logs for long series like the RGL s7 6s grand finals
  
• There is now an API for querying for players and logs. It is pretty basic at the moment because it is just for internal use. If anyone is interested in using the data from trends.tf, please send me patches for improving the API :)

Once again, please send me any bugs or suggestions you have either on Discord, Steam, or as a reply in this thread.

Thanks :)

https://logs.tf/api/v1/log has been dead since yesterday

ninja edit: main page down now too :L

joined and crashed steam lmao

I've been holding off on importing all the logs

• so I can work out the kinks in the importer
  
• so I can work on the performance (more data means slower site)
  
• until I migrate to a server with a larger disk

This will give incorrect results. You need to use respawns and not deaths, since you always respawn at the start of each round. Unfortunately, this is not recorded by logs.tf. Really, the only way to fix this would be to use an alternative parser.

Feature update:

• You can now view logs on the site. It is possible to combine up to five logs and view them just like an individual log. This should hopefully make manual log combiners mostly unnecessary.
  
  Some stats are not displayed. Medic stats like "average time before healing" are not displayed because it is impossible to display them accurately for multiple logs. In the future, I may display them as a list. Other stats like killstreaks and per-round stats are not currently extracted from the log summary information.
  
• Replaced the trends chart library with C3.js (thanks Bv!). This should help with performance.
  
• You can now vary the size of the rolling average on the trends page.
  
• There are now links to RGL, UGC, ETF2L, and OZFortress on player profile pages.

I've come to make an announcement: Sigafoo the RGL admin's a bitch-ass motherfucker. He banned my fucking alt. That's right. He took his discord fuckin' moderator dick out and he banned my FUCKING alt, and he said his dick was THIS BIG, and I said that's disgusting. So I'm making a callout post on my TeamFortress.tv. Sigafoo the RGL admin, you got a small dick. It's the size of this second banana except WAY smaller. And guess what? Here's what my dong looks like. That's right, baby. Tall points, no quills, no pillows, look at that, it looks like two stickies and a rocket. He fucked my alt, so guess what, I'm gonna fuck TF2. That's right, this is what you get! My SUPER CROCKET PISS! Except I'm not gonna piss on TF2. I'm gonna go higher. I'm pissing on STEEEEEAM How do you like that, GABEN? I PISSED ON STEAM, YOU IDIOT! You have twenty-three hours before the piss DROPLETS hit the fucking game, now get out of my fucking sight before I piss on you too!

Feature update:

• Avatars are now displayed on player profiles, search results, and on the leaderboard and peers pages. Player pages now use their name on steam.
  
• I added a temporary site logo/favicon. I am still looking for someone to design a proper one.
  
• The totals page now shows averages either per minute (for damage) or per 30m (for kills, etc.).
  
• The weapons page now shows totals for kills, damage, logs, and time played.
  
• There is now a discord which you can use to suggest features or report bugs.

Some logs return 500 errors starting at https://logs.tf//3001608 and ending at https://logs.tf/3001646

For a "fun" example of when this happens, see https://logs.tf/2726837

Feature update:

• You can now sort the logs, peers, and weapons pages by (almost) every column. So e.g. you can find your highest DPM log, or the player you have the best winrate with.
  
• There is now a leaderboard which ranks players by winrate with 50 wins/losses added (to help filter out players who have 100% winrate over 5 games). You can also sort by raw winrate, time played, and number of logs played. In addition, you can filter by class, map, and format, making it easy to answer questions like "Who's the best pyro player in Prolander on koth maps". Currently, leaderboard stats are recalculated every night.
  
• And just for glass, I added the overview stats (winrate, W-L-T, etc.) to the totals page so you can filter by class.

Hm, that's a good idea. Previously, player_last was a table, which I suppose is a kind of manually-materialized view.

Nope. Please send a PR :)

This is being tracked by this issue. But it's not very high on the list of priorities atm. Though part of the reason for switching to postgres in the first place was so I could have multiple processes modifying the database at once, such as a process which calculated elo.

I want to start scraping RGL at some point (see this issue). Unfortunately, RGL doesn't really have an API, so I'd have to scrape their site :l. Honestly, if ETF2L has an API I would look into them first.

Can you link? Thanks.

Nope, sorry. I'm working on adding filters for every page on the site, but the overview hasn't gotten that treatment yet. Though perhaps I could just add this to the totals page...

Basically this. At the moment there is not too much processing on top of raw stats from logs.tf. So if/when I write my own logs parser we can address this. But until then pyro will always have like 3x the hits vs shots.

Winrate is calculated based on games with at least ⅔ time on this class. You can hover over the column headers and the tooltip will show some of the criteria. DPM, accuracy, and time played are based on all times you played that class.

I didn't have much of a choice :)

(that being said, if anyone can help me make a logo/favicon or can help with the CSS, I'd appreciate it)

Ok, I've addressed most of the major performance issues. The responsiveness should be back to what it was before the migration. I'm still importing logs from the past week, but it is going much faster than it had been.

Here's the explain analyze output for the peers query, which is currently the slowest page on the site. And here is the schema. My current plan is to move most columns out of the round table to reduce the amount of data we have to read in that inner loop to determine win/loss statistics.

A little update:

I'm migrating the database from SQLite to PostgreSQL. I started this last week, and did the switchover this past weekend. However, some of the queries are now taking way longer than they used to. I am currently working on this. Availability might be a bit spotty until I can get to the bottom of things. I am also trying to get log importing back up, but that is going much slower than before too. Please be patient for the next few days :)

In the longer term, performance was and is a big problem with the site, even before switching databases. I would love if some more experienced developers could look over my schema/queries and help out.

Good idea. I made an issue for it.

edit: Seemed really simple, so I just added it. Have fun ;)

Yeah, I'd like to add some kind of elo eventually. But there are a lot of other things which need doing first.