A log parser for Counter Strike: Global Offensive
CS:GO dedicated servers can write game logs to a file. These contain details about actions that occured in the game, such as a player attacking another player, getting a kill or assist, planting/defusing the bomb, rescuing a hostage, etc. Even chicken deaths are logged!
The simplest way to build from source is using CMake (version 3.15 or above is required). For example:
git clone git@github.com:rufus-stone/csgo-log-parser.git
cd csgo-log-parser
# Get CMake to create a new build directory
cmake -S . -B build
# Build the app
cmake --build buildcsgoparse requires the following libraries:
If these are not already installed on your system, CMake will fetch them from GitHub for you
csgoparse loads settings from a config.json file, which, if necessary, it creates the first time the program runs.
The barebones config.json looks like this:
{
"log_dir": null
}Out of the box, this requires modification by the user to tell csgoparse which directory contains your game server logs (e.g. <server install dir>/server/logs), so update the "log_dir" entry with a string specifying the path to your server log directory (fully qualified paths only; no '~' appreviations or similar!). For example, on Linux:
{
"log_dir": "/home/somebody/csgo/server/logs"
}Because CS:GO server logs use a player's Steam ID to differentiate between players, and because a player can freely change their display name in-game, csgoparse also uses the Steam ID to identify players when tracking stats. However, should you wish, you can tell csgoparse to translate specific Steam IDs into some other text, as this may make player-specific searches in programs like Elasticsearch/Kibana easier. In this way, it does not matter whether a player changes their in-game display name, csgoparse will continue to track their stats via their Steam ID, but output events containing whatever alternative name you specified in the config.json file. For example:
{
"log_dir": "/home/somebody/csgo/server/logs",
"steam_id_translation": {
"active": true,
"translations": {
"STEAM_1:0:12345678": "Alice",
"STEAM_1:1:87654321": "Bob"
}
}
}The config above will ensure that, should csgoparse process a server log line containing references to Steam ID "STEAM_1:0:12345678", it will replace this with the name "Alice" when generating output JSON. Likewise, "STEAM_1:1:87654321" will be translated to "Bob". Any other Steam IDs will remain unchanged. The "active" setting can be changed to false in order to disable the Steam ID translation functionality.
Alternatively, rather than providing per-Steam ID name translation, you can opt to use a hash of the Steam ID instead (MD5, SHA1, and SHA256 are currently supported). For example:
{
"log_dir": "/home/somebody/csgo/server/logs",
"steam_id_translation": {
"active": true,
"hash": "md5"
}
}The config above will replace all Steam IDs with their MD5 hash (replace "md5" with "sha1" or "sha256" to use those hashing algorithms).
You can also mix and match hashes with per-Steam ID translations if you wish - csgoparse will use the specified translation if one exists for a given Steam ID, but will fall back on the hash if no translation is found. For example:
{
"log_dir": "/home/somebody/csgo/server/logs",
"steam_id_translation": {
"active": true,
"hash": "sha1",
"translations": {
"STEAM_1:0:12345678": "Alice",
"STEAM_1:1:87654321": "Bob"
}
}
}The config above will ensure that, should csgoparse process a server log line containing references to Steam ID "STEAM_1:0:12345678", it will replace this with the name "Alice" when generating output JSON. Likewise, "STEAM_1:1:87654321" will be translated to "Bob". All other Steam IDs will be replaced with their SHA1 hash.
csgoparse currently expects CS:GO server logs to be created using the maximum logging verbosity level
- TODO: Allow for varying levels of server log verbosity