CFTracker 1.7 + UserVoice
June 17, 2010 6 Comments
CfTracker
CfTracker 1.7 is now available with the following changes:
- Applications and sessions have been split into two pages.
- Sessions can now be “stopped” instead of trying to force expiration (much better approach).
- You can perform a stop or refresh on multiple sessions by their client IP (further properties to be added soon).
- Tooltips that try to explain the various buttons and table headers (will provide option to disable in the next version).
- New logo! As seen above.
- Addition information in the footers. Added links to CfTrackers various resources (github, my blog, riaforge, uservoice).
I want your suggestions
I’ve created a UserVoice site for CFTracker (http://cftracker.uservoice.com) so users can provide their own suggestions as to new features and see what mad ideas I have planned. The site will allow you to vote against the various ideas or submit your own and then see feedback from others and my thoughts / progress on them. I know at least a couple of people have been using CfTracker and like it so I’m hoping to make it as useful as possible.
Download 1.7
http://github.com/misterdai/cfTracker/downloads
About misterdai
Found something extremely useful and want to thank me with more than just words?
Hi,
Nice stuff,
Can this be installed as part of an application and not CF Admin, just for security reasons?
Thanks
mike
@mike,
Currently it’s tied into the CF Admin but I can’t see any reason why it couldn’t run outside if needed. All you need to do is remove the includes for header.cfm and footer.cfm. Obviously you’d have to link to status.cfm and index.cfm yourself then.
I put it in the CF Admin as it felt like the sort of tool that should be in there and I then didn’t have to worry about adding any security to it for access.
Let me know how it goes running it standalone and add it as an idea to the uservoice site (see links above) if you want that supported in future versions
@Mike: just installed and had a quick play. Looks amazing! Well done. I can see this as being very useful. How “safe” is it to deploy to production? Does it use up much memory etc?
@Matthew
Glad you like what you see. It’d be great to hear any use cases you have for a tool like this.
It should be pretty memory safe as nothing is stored in any persistant scope (app, server, session) and there isn’t any constant task running in the background. I’ve made it CF8+ only as well since I didn’t want it refreshing session timeouts when it retrieves their values. I haven’t got a well used CF8+ production server I can try it out on but John Wish (http://bit.ly/9LKuJ8) has used it on production and killed 500 sessions that a search engine had created.
I’m currently working on the next version that’ll work standalone, like Mike has asked for above, using FW1 as a base. It’ll also provide a way to view the query cache, selectively purge individual items and view their result sets.
Will it work on Railo?
@Sebastiaan,
I’m really hoping to get a Railo version out at some point. At the moment I’m converting it to use FW1 as a base (which should be Railo compatible), making it less tied into the CFIDE administrator. The tricky bit will be finding out if Railo has similar methods for stopping / refreshing / viewing applications and session scopes. If they have then things should be simple, if they haven’t then certain functionality would have to be disabled until a workaround can be found.
I like Railo and would love for CFTracker to work on it, but currently I live in Adobe CF land which is why I’ve focused on that first.