So I'm working on a project that I was introduced to a year ago. One of the features of project involves alarming the users when certain events are triggered. There is also a log of these events. First you need to understand this:Not all alarms generate event logsEvents can be logged without generating alarms.The design of this involves flat files that hold a bunch of information about the events and the alarms. This includes everything from where the alarms are sent, priority levels, etc.What happens in the code is when an event is trigger, it sends a message with a bunch of data attached to it to a process that reads in the flat files, replaces the data appropriately, and then routes it.My question is this:Is it normal design to save all this information outside of the code. We're running into problems when we deploy because we have to ensure that the flat files and the code are in sync. It's created some troubleshooting nightmares, and it honestly just feels like more hassle then just having a class dedicated to this stuff, and shipping it with the code.
Flat files for events and alarms
design;c++;architecture;system