Hi,
I only started using the quick log the other day. One major issue I find is that is does not scroll or add new events to the list as they happen. This would be really usefull to look at the screen and see the last 10 or 20 events without having to close and reopen the quick log again.
Thanks,
Quick Log
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Quote from manual:
Regards,
Max
So, you should set logging mode for the test to "Reply" or "Full" and HM will be refresh log pane when status changes.When you select menu “View”->”Quick Log”, HostMonitor opens a pane located at the bottom of the main window and displays last 10 events for selected test or 50 events for selected folder (folder's list includes last events for every test within the folder).
The term "event" means a log record that was added with every test status change. If logging mode for the test is set to "Reply" or "Full", HostMonitor will add a new record when test status changes or the value of "Reply" field changes.
Regards,
Max
Hi,
Thanks for the quick response.
I did see that, but I don't want full logging, just status changes.
My reasoning is this. At the moment, I only trigger alerts after a certain threshold, however, it's nice to look at the log and see if anything 'looks' a bit ropey. At the moment, there are always a lot of remote tests that fail once and come back up before an alert ever triggers.
With logging set to 'default', which is what I want, the quick log never seems to update unless you click out of it and back in. It'd be nice if it refreshed automatically so I could see any brief alerts that didn't trigger an actualy alert.
Does this make sense?
Thanks for the quick response.
I did see that, but I don't want full logging, just status changes.
My reasoning is this. At the moment, I only trigger alerts after a certain threshold, however, it's nice to look at the log and see if anything 'looks' a bit ropey. At the moment, there are always a lot of remote tests that fail once and come back up before an alert ever triggers.
With logging set to 'default', which is what I want, the quick log never seems to update unless you click out of it and back in. It'd be nice if it refreshed automatically so I could see any brief alerts that didn't trigger an actualy alert.
Does this make sense?
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Ok. Why do not you want to use "Reply" mode?pjsmith wrote:I did see that, but I don't want full logging, just status changes.
"Reply - record information into log every time the status or reply value of the test changes."
In such case I do not understand why do you need Quick log at all, if you may look at the same information on Test Detail Area? Anywhere, you may set logging mode up for certain tests to "Reply" and for other tests leave it "Default". Could you try it?pjsmith wrote:My reasoning is this. At the moment, I only trigger alerts after a certain threshold, however, it's nice to look at the log and see if anything 'looks' a bit ropey. At the moment, there are always a lot of remote tests that fail once and come back up before an alert ever triggers.
With logging set to 'default', which is what I want, the quick log never seems to update unless you click out of it and back in. It'd be nice if it refreshed automatically so I could see any brief alerts that didn't trigger an actualy alert.
Does this make sense?
Regards,
Max
Unless I'm missunderstanding, I don't want reply mode. For instance. A ping test, the reply changes all the time, but I only want data logged when the status changes, ie the test fails and triggers an alert. I've a lot tests where the value changes all the time (every 10 secs), so I don't want logging of reply data or the quick log window to update every time a reply value changes. It'd be scrolling quicker than I could read it 
I want an overview of tests that have failed recently, but not triggered alerts (as my alert threshold is more than 1 failed test). The quick log would enable me to see the events fail as they fail, and this is originally what I though it was for. Many of my ping tests for instance will time out on occasion, but will not trigger an alert unless they fail, say 5 times in a row. I would however like to keep an eye on things by monitoring a scrolling window to see if that test is intermittant, i.e. it might fail and come back many times but not actually trigger an alert. It's useful information to know, at least it gives you a better picture of what is going on with your tests.
Using the 'test detail' window I would have to click on every test to check them. ot really practical.

I want an overview of tests that have failed recently, but not triggered alerts (as my alert threshold is more than 1 failed test). The quick log would enable me to see the events fail as they fail, and this is originally what I though it was for. Many of my ping tests for instance will time out on occasion, but will not trigger an alert unless they fail, say 5 times in a row. I would however like to keep an eye on things by monitoring a scrolling window to see if that test is intermittant, i.e. it might fail and come back many times but not actually trigger an alert. It's useful information to know, at least it gives you a better picture of what is going on with your tests.
Using the 'test detail' window I would have to click on every test to check them. ot really practical.