Open laurenassour opened 1 month ago
I'm a little confused on the phrasing here - to who and why are we giving "clear start/stop criteria"?
Very fair! In the software I manage, on start up we publish very specific messages that denote that it is starting up: ex:
==**==
STARTING Tracking service
Start time: 2024-06-20 09:00:00.001550+00:00
Version: 2729a
Command line: ['.venv/bin/python3', '-m', 'app.tracking_service', '--market', 'US', '--version', '2729a']
==**==
We don't publish anything for shutdown, but I could see a case where someone might. So, alogamous should be able to take configuration from users that defines what a startup looks like and what a shut down looks like, to help it track starts/stops of a process. This could be useful in tracking logging changes across instances vs different log files.
Our services have clearly defined start up log messages - make these configuration in alogamous to give clear start/stop criteria if they're all contained in the same log file (like ours are).