Prerequisite software is easily obtained and installed through handy links provided in Sift's installation document. For my tests, the target server had .Net redistributable 1.0 and .Net Framework SP2, so all that was required was a quick download and installation of the .NET J# redistributable (required because Sift's server-side components were developed in J#).
Once Sift was installed, I was prompted to log in. Normally, I wouldn't mention such a mundane step, but this is one area where Sift needs some work. There is no administration required for users because there is no user administration.
While Sift takes advantage of integrated windows authentication through IIS in regard to access to Web services, this does not apply to users of the Sift
console. Service Integrity is aware of this issue and is working on a more integrated solution for user administration.
|
Good
• In-depth monitoring of .Net Web services
• Real-time dashboard and alerts
• Centralized console
Bad
|
It's a breeze to add a host and discover services on that host automatically, provided the services are only one directory deep in the server hierarchy. Services can be added manually, but the autodiscovery feature makes the addition of numerous services simple. After the services have been added, Sift begins logging access to each service and subordinate operation, making the data available for viewing in the dashboard, reports and alert generation.
The dashboard provides an almost real-time display of server and service metrics from a multitude of views. Although the physical layout of the dashboard is not configurable, you can add multiple individual panels, each configured with a metric-appropriate graphical chart.
I added graphs detailing
server performance, access counts per service and response times per service.
Test Driving Sift
I fired up ApacheBench and sent requests to a service being monitoring by Sift. The panels in the dashboard run about one to two minutes behind in display of data, but the eye-candy helps to discern at a glance the state of your .Net Web services. It was easy to see the difference between the two Web services I'd coded up and deployed in terms of response time and usage.
Reports come in three distinct metric categories to view: performance, traffic, and usage of services and operations. Reports reside on the dashboard and let you segment real-time displays and reports into separate categories.
Lori MacVittie is a Network Computing technology editor working in our Green Bay, Wis., labs. Write to her at lmacvittie@nwc.com.
Post a comment or question on this story.
RSS
