View previous topic :: View next topic |
Author |
Message |
seelye
Joined: 17 Sep 2005 Posts: 40 Location: USA
|
Posted: Thu Jan 12, 2017 6:23 pm Post subject: Variable usage in Private Log Path |
|
|
I have a two fold question.
First, it appears that when I use a Private log and use the same log file name for multiple tests that the log will of course contain the replies for all of those tests. That's expected behavior but makes it difficult when we are trying to view these using the TEST->View Private Log menu option.
So, for the tests where I want a private log, I'd like to use variables to uniquely identify a private log for each test. This way we can more easily script and copy tests.
So my question is: I know I am allowed to use certain variables in the path such as %YYYYMMDD% and others such as self established Folder variable such as %fvar_system_prefix%
However I'd like the ability to use %TestID% and perhaps %TestName% in the path/filename field for Private Logs.
Is there a reason these variables are not available or could all variables that are related to a particular test be permitted in this field?
Thanks for your consideration and explanation if this cannot be done. |
|
Back to top |
|
|
KS-Soft Europe
Joined: 16 May 2006 Posts: 2832
|
Posted: Thu Jan 12, 2017 7:12 pm Post subject: Variable usage in Private Log Path |
|
|
1. You may use menu Test -> Log Analyzer it will pick up private log and show records, related to selected test item.
2. Private Log path may contain "Test properties variables":
http://www.ks-soft.net/hostmon.eng/mframe.htm#tests.htm#testpropvariables
E.g.: Private log path may look like the following:
D:\HMLogs\%FolderFullPath%\%MethodName%-%HostAddrB%.htm |
|
Back to top |
|
|
seelye
Joined: 17 Sep 2005 Posts: 40 Location: USA
|
Posted: Thu Jan 12, 2017 9:04 pm Post subject: |
|
|
Thanks for the prompt reply but that doesn't quite solve the problem.
Except me, my system admins always use RCC when accessing HM. Therefore wouldn't we'd need a Log Analyzer license for each system admin? And they really just need a method for them to view more than the quicklog raw data that is stored natively in the HML.
Also using the Test Property Variables such as %MethodName%%HostAddrB% might work to generate unique logs, but is there a reason that %TestID% isn't available? I understand that when using %TestID%.
Granted %TestID% is a bit cryptic but seems very stable for our particular usage.
Thoughts?
I have another question about the Log Analyzer performance when opening a range of Text log files. If you want, I can start a new post but this is somewhat related to why I'm not so keen on the use of the Log Analyzer for log files with multiple tests is:
Example: when I open a month worth log file that captures PING, SNMP data for 22 tests (all logged to the same TEXT log and a new log are created each day) it takes a VERY long time. due to the sorting and log analyzer processing of each file. It's done this for years with different computers and simply seems to be due to how it opens, sorts, and processes each file. It works well for single days but often all I want it to view lots of days for a single test so having those test results stored separately would help. |
|
Back to top |
|
|
KS-Soft
Joined: 03 Apr 2002 Posts: 12801 Location: USA
|
Posted: Fri Jan 13, 2017 8:04 am Post subject: |
|
|
implemented %TestID% for private log.
Link for update sent to your e-mail
Regards
Alex |
|
Back to top |
|
|
|