Description
Hi, thank you for your work on Keyhole and Hatchet, both tools have proven incredibly valuable for me when identify areas of improvement within Mongo.
I have setup a Github actions pipeline to download server logs periodically using the atlas cli:
atlas logs download <host> mongodb.gzAfter downloading the log, I attempt to generate a Hatchet report, and then run the web server to collect data from the api:
# Generate the hatchet, run report build to completion.
hatchet /tmp/mongodb.log.gz
# Once done run the API server.
hatchet -web &
However, every so often the hatchet fails to process a log file at random with the following error:
# 'broken' is the name of the file that I pulled from Github as an artifact
2023/03/28 17:04:00 Downloads/hatchet v0.3.4-20230327
2023/03/28 17:04:00 processing broken-00-01-mongodb.log.gz
2023/03/28 17:04:00 hatchet name is broken_00_01_mongodb_169960
2023/03/28 17:04:00 log format not supportedI understand that this is likely an issue with the file generation, or contents of the file itself, meaning that there is a chance that the issue lies in the Atlas CLI.
However, I was wondering if there was any way to get more specific information about this error, as running in verbose mode did not yield any extra information.
Any help appreciated if you happen to have ran into this issue before.
Thanks
Versions
$ hatchet -version
Downloads/hatchet v0.3.4-20230327
$ go version
go version go1.20.2 linux/amd64
$ atlas process list
ID REPLICA SET NAME SHARD NAME VERSION
atlas-xxx-i-00-00.yyy.mongodb.net:27017 atlas-xxx-shard-0 4.4.19
atlas-xxx-shard-00-00.yyy.mongodb.net:27017 atlas-xxx-shard-0 4.4.19
atlas-xxx-shard-00-01.yyy.mongodb.net:27017 atlas-xxx-shard-0 4.4.19
atlas-xxx-shard-00-02.yyy.mongodb.net:27017 atlas-xxx-shard-0 4.4.19