The one that sticks out in my mind is some flexibility to do recurring downtime. Right now you can schedule downtime on a one-off basis. I'd like to be able to schedule application downtime if I know the application I'm monitoring is going to be down, and the one I'm responsible for needs to go down every night for a scheduled recycle. I have to schedule it everyday manually, but I would love to say, "Every night at 2:00 in the morning it's going to be down, so don't monitor it for an hour." This would prevent false positives saying that the application's down. That's one thing I would really like. Also, I would like more granular reporting capability, and a larger breadth of a time period that I can run a report for. I'd like to get more granular with the data points that I'm capturing as far as what my performance metrics were. Right now it's averaged, so I get an average. I think I get some standard deviation from the average. I would like the actual data points if I need them. I would like to have that data broken out by the machines that I'm monitoring and not rolled up into one data point. This would enable me to see trends with actual data as opposed to just averages. We monitor applications, for example, from five different machines. I'm running the same transaction on five different machines, but when I run the report it's aggregated, but I want to be able to split that up. That would help me know how one site is performing over another. I can get it at a high level but then I like to be able to use the granular data to maybe back into when exactly things start going awry, which I might not get from just an average and standard deviation. Having these data points maybe helpful to our development team with some analytics, from a transaction standpoint, maybe starting to know when a transaction trended towards bad.
![AppPulse Suite [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_100/durwsc3z47nd2vx5dltpkmpv49gk.jpg)
