Jevik-R/Log-Ingestor — reverse-engineered prompt

Build me a PostgreSQL project for managing logs from lots of distributed servers. I want the database to store logs in a structured way, split server wise so each server’s logs are easy to query without everything ending up in one giant table. There should be a central table that keeps track of each server, like its server id, IP address, provider, and the log format it uses, and then separate log storage for things like system logs, application logs, security events, and production logs.

Please include the full database design, the table creation SQL, enough sample data to show multiple servers and log types, and a set of useful SQL queries someone could run for real analysis. I care about things like server health monitoring, crash detection, brute force or suspicious login detection, traffic and peak hour analysis, uptime, and session based cost summaries. Keep the schema well normalized and make the queries feel practical for admins, security teams, and developers. If needed, look up current PostgreSQL best practices online.