It's a very Salesforce Friday; the weather is nice, my fingers are flying, and most importantly my code is saving without errors!
I'm hoping the description got your attention on this one and you wondering how in the world Salesforce is going to monitor your servers. Well, I've fed your assumptions a half-truth. At this point, Salesforce isn't going to be doing the monitoring (yet?); it will be simply providing to you notifications.
I know, I know - you've got high-end systems in place doing all the server monitoring you could ever dream of full of alerts, notifications, bells, whistles, and some Rita's Water Ice on top of that too (you know, in honor of it being Spring). Don't overlook the point of this series; it isn't to just create a custom object that will trigger some workflow. It's about being able to tie together three or four different pieces of software to build an entire system that leverages the flexibility of Salesforce (and because all roads will inevitably lead to Salesforce). Not just a system, but something that can easily be expanded an built upon.
Here's what I'm thinking:
Monitor a server
Use Perfmon - Memory Usage
Use a command-line utility - Hard disk utilization
Create Alerts
What's wrong with who
Import Process
Get that info into Salesforce so we can use it
Where's the data going to live?
Dashboard/Workflow
What are you going to do with that data?
Stay tuned! We're going to have some fun with Perfmon, batching, Data Loader, and some VF.
