Help need on writing use case for a enhanced logging implementation
Mystic last edited by user
I am writing a functional design for enhancing our existing application logging. Our Core application is built on C and we have a integration layer on top of that to talk with other third party systems. Until now, we do not have a centralized logging mechanism where one would be able to track the entire transaction with the help of one Unique ID. After implementing this design, we are hoping we would be able to achieve it.
We have created 5 different database tables:
As these tables gets populated we will hand over the SQL query to Foglight for application performance monitoring.
Question: How do I write use cases for this implementation before I hand it over to my QA. Because I have to include all the integration points in my FD.
I would welcome your thoughts on it.
My perspective of this question is in terms of scenarios and how it will be handled. There are different use cases which may fall in this criteria. Logging on different tables for different scenarios
- Example #1 - Disk Space issue, When there is insufficient disk space available for MSSQL, Other processing this would go into Err_Log, System_Event_Log
- Example #2 - When there is timeout of operations (network, I/O issues it need to be captured)
- Example #3 - When the CPU exceeds 80% it need to be captured and logged in System_event_log
- Example #4 - When there is error in processing (Invalid data formats, error thrown by application) it will be logged in error_log
- Example #5 - Archival mechanism of this logs (How frequently they needed to be cleaned up)
- Example #6 - If the same error is occured multiple times do you increase severity / prompt for immediate attention
- Example #7 - Identity failures, frequency of failures for Errors