This is basically a request for help in designing the database / objects for CFTracker version 3. I’m struggling to decide on the best way to handle and structure the data and would love to get some input or even your own ideas on how it’d be designed. Currently this is the main reason I’m not getting anywhere with version 3, as I don’t want to progress too far and then have to rip everything apart again.
I’ve created a Google document that describes the data I’m most concerned with and their relationships. It contains all the details I figured would be needed and some contact information, although I’m happy for comments to be added here as well.
For those of you who haven’t heard of CFTracker before. It’s an open source, CFML based application that lets you monitor your ColdFusion server and inspect various internal aspects of it, such as Session, Applications, Query Cache, Threads, Memory pools. The current version only monitors the instance that it’s installed to and supports CF8/9 and Railo.