Ipswitch Forums / Ipswitch Products / WhatsUp Gold / Logical Disk Counters--What's wrong? / Latest Posts

RE: Logical Disk Counters--What's wrong?

an-D — Tue, 07 Oct 2008 20:35:08 GMT

nice script, works nicely for me on all of our servers. Did have a few issues when i realised we had 2x devices with the same IP for some reason, but deleting the bogy fixed it!

1 question though, how can i make the script alert me at 25% and then again at 10% free space?

Cheers

RE: Logical Disk Counters--What's wrong?

oby — Wed, 10 Sep 2008 16:46:04 GMT

Error: Source:'ADODB.Recordset'
Line:77 Char:2
Error:0 'Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.'
-v
(null)

We got the same error on selected server. Any ideas? It must be a database problem, because the "Disk Utilization Performance Monitor" get results from the server. I deleted the server and added it again to whats up. But that didnt change my problem. The Script cant add the Disk_Space_Results attribute and ignores the Disk_Space_Thresholds attribute. Perhaps we can delete all database stuff referenced to the broken devices. I dont know how...

RE: Logical Disk Counters--What's wrong?

jchong — Tue, 02 Sep 2008 16:45:40 GMT

[quote][b]jchong (8/28/2008)[/b][hr]Thanks for the great script - I'm using it on all my Microsoft Windows based severs.

Does anybody know if this can be used with linux based servers? I have disk utilization setup for the linux servers and created the following attributes for the server:

Disk_Space_Thresholds
/var=15%;/home=10%;/usr=15%

I get the following error when testing:

Error: Source:'Microsoft OLE DB Provider for ODBC Drivers'
Line:76 Char:2
Error:0 '[Microsoft][ODBC SQL Server Driver][SQL Server]Divide by zero error encountered.'
-v
(null)
[/quote]

Some unix devices (Exampe: /sys, /var/lib/nfs/rpc_pipefs, /proc/sys/fs/binfmt_misc) are listed as having 0 space available which caused problems with the SQL query.

The following changes to the code fixes this problem (line 75 - see [b]bold text[/b]):

sSql = "SELECT SDI.sDescription, SD.dPollTime, D.sDisplayName, (1 - SD.nUsed_Avg / SD.nSize) * 100 AS perc, (SD.nSize - SD.nUsed_Avg) / 1073741824 AS giga, (SD.nSize - SD.nUsed_Avg) / 1048576 AS mega FROM Device AS D INNER JOIN PivotStatisticalMonitorTypeToDevice AS PSM ON PSM.nDeviceID = D.nDeviceID INNER JOIN StatisticalDiskIdentification AS SDI ON SDI.nPivotStatisticalMonitorTypeToDeviceID = PSM.nPivotStatisticalMonitorTypeToDeviceID INNER JOIN StatisticalDisk AS SD ON SD.nStatisticalDiskIdentificationID = SDI.nStatisticalDiskIdentificationID [b]AND SD.nSize > 0[/b] WHERE D.nDeviceID = '" & nDeviceID & "' AND SD.dPollTime = (SELECT top 1 SD.dPollTime FROM Device AS D INNER JOIN PivotStatisticalMonitorTypeToDevice AS PSM ON PSM.nDeviceID = D.nDeviceID INNER JOIN StatisticalDiskIdentification AS SDI ON SDI.nPivotStatisticalMonitorTypeToDeviceID = PSM.nPivotStatisticalMonitorTypeToDeviceID INNER JOIN StatisticalDisk AS SD ON SD.nStatisticalDiskIdentificationID = SDI.nStatisticalDiskIdentificationID [b]AND SD.nSize > 0[/b] WHERE D.nDeviceID = '" & nDeviceID & "' ORDER BY SD.dPollTime DESC) ORDER BY SDI.sDescription"

This causes the query to ignore devices which have 0 size. After making this change, I'm able to use this script with my linux servers as well.

RE: Logical Disk Counters--What's wrong?

jchong — Thu, 28 Aug 2008 10:18:41 GMT

Thanks for the great script - I'm using it on all my Microsoft Windows based severs.

Does anybody know if this can be used with linux based servers? I have disk utilization setup for the linux servers and created the following attributes for the server:

Disk_Space_Thresholds
/var=15%;/home=10%;/usr=15%

I get the following error when testing:

Error: Source:'Microsoft OLE DB Provider for ODBC Drivers'
Line:76 Char:2
Error:0 '[Microsoft][ODBC SQL Server Driver][SQL Server]Divide by zero error encountered.'
-v
(null)

RE: Logical Disk Counters--What's wrong?

Tommyboy — Tue, 26 Aug 2008 15:30:24 GMT

[quote][b]nickcarbone (5/21/2008)[/b][hr]

After applying the script i get the following error message when testing it against a server.

Error: Source:'ADODB.Recordset'
Line:77 Char:2
Error:0 'Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.'
-v
(null)

Any ideas?[/quote]

OK, I am getting this exact error on select servers but not others. It's driving me crazy.

RE: Logical Disk Counters--What's wrong?

Tommyboy — Thu, 21 Aug 2008 12:17:46 GMT

Hey, I wanted to thank everyone who made this script.

I have one interesting issue though; it's not working for some servers. I look in attributes of the working and non working servers and noticed something interesing. On the servers where the script works, I will see a 'Disk_Space_results' attribute with the appropriate results, but it is missing on the non-working servers. Any idea why?

RE: Logical Disk Counters--What's wrong?

pscad00 — Wed, 30 Jul 2008 15:25:14 GMT

The disk monitor script does work in WUG12. I just recently upgraded and have been using it for a week.

Pat

RE: Logical Disk Counters--What's wrong?

bbrinkman — Mon, 23 Jun 2008 14:57:30 GMT

not sure why, but I can't delete this post. Question retracted I found my mistake.

RE: Logical Disk Counters--What's wrong?

Elipsis — Tue, 03 Jun 2008 10:55:46 GMT

[quote][b]MB - NS (2/8/2008)[/b][hr]
There are some scripts around which use directly the values retrieved by the Disk Utilization perf monitors.

The one I wrote also allows you to specify the thresholds using the device attributes (enclosed in this post). This way you avoid having multiple monitors depending on the letters and thresholds you need. Please note that you need to have 'disk Utilization' enabled and working on the device.[/quote]

This script is WONDERFUL, and saved my ***. :)

RE: Logical Disk Counters--What's wrong?

MB - NS — Fri, 30 May 2008 07:30:43 GMT

[quote][b]nickcarbone (5/28/2008)[/b][hr]I am getting the same error message on each server i try.[/quote]

Then I really don't know. Do you have access to a SQL Enterprise Manager ?

If yes, then try to run the SQL query directly using this tool, to see what you get.

[quote]Hi MB-NS, thanks for the script, it works on all the Win2k/2k3 servers except one Win2k server.

I'm getting this error during the Active Script Monitor Test:

Error: Source:'Microsoft OLE DB Provider for ODBC Drivers'
Line:76 Char:2
Error:0 '[Microsoft][ODBC SQL Server Driver][SQL Server]Divide by zero error encountered.'
-v
(null)

FYI:I'm running WUG Ver. 11

Disk utilization perfmon is enabled but I can't get any results in the reports.

So does this error mean there are some kind of problem with the WMI?

Thanks in advance,

Tony[/quote]
It does not use WMI at all, but only SNMP.
Please check that :
1- SNMP credentials are set on the device.
2- the SNMP is installed, running and configured with the correct community (these settings are on the service settings, in the services.msc snapin), and also that the WUG IP is allowed (same place).

RE: Logical Disk Counters--What's wrong?

skyrix — Thu, 29 May 2008 15:32:18 GMT

Hi MB-NS, thanks for the script, it works on all the Win2k/2k3 servers except one Win2k server.

I'm getting this error during the Active Script Monitor Test:

Error: Source:'Microsoft OLE DB Provider for ODBC Drivers'
Line:76 Char:2
Error:0 '[Microsoft][ODBC SQL Server Driver][SQL Server]Divide by zero error encountered.'
-v
(null)

FYI:I'm running WUG Ver. 11

Disk utilization perfmon is enabled but I can't get any results in the reports.

So does this error mean there are some kind of problem with the WMI?

Thanks in advance,

Tony

RE: Logical Disk Counters--What's wrong?

nickcarbone — Wed, 28 May 2008 14:00:53 GMT

I am getting the same error message on each server i try.

RE: Logical Disk Counters--What's wrong?

MB - NS — Wed, 28 May 2008 04:36:24 GMT

Do you have several devices with the same IP address, by any chance ?

Does the script work on some devices, or none at all ?

RE: Logical Disk Counters--What's wrong?

nickcarbone — Tue, 27 May 2008 12:29:21 GMT

' %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
' %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
' This script is a merge of 2 scripts. Credits go to :
' - XXXXX's , which use the performance monitors values to test the disk space, and most code for this script.
' - YYYYYY's, which retrieve the thresholds from a specified attribute
' I added the feature that, if the given attribute is not set, you can use a default value for all disks.
' Also, specifying a threshold of 0 disables the check on that disk. You must always specify the unit (%, G or M), even when disabling the check.
' Format for the thresholds are something like this : 'C:\=10%;D:\=5G;E:\=650M;G:\=0%'
' THE DRIVE NAME IN THE ATTRIBUTE MUST BE THE SAME AS THE ONE RETURNED BY THE DISK PERF MONITOR. (e.g. for Windows : C:\, D:\, and so on...)
' You can see see the name of each drive by using the Test button and scanning the result.
' %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
' %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

' Name of the attribute which will contain the specific thresholds
THRESHOLDS_ATTRIBUTE = "Disk_Space_Thresholds"

' Name of the attribute which will contain the result of the check. Automatically created.
RESULT_ATTRIBUTE = "Disk_Space_Results"

' If the threshold attribute is not found, should the monitor report as DOWN ?
' If set to False, it will use the default value for all disks.
DOWN_NO_ATTRIBUTE = true

' If there are no recent performance entries for at least one device, should the monitor report as DOWN ? - NOT IMPLEMENTED
DOWN_ON_AGED_VALUES = true

' MAX_AGE value specify the maximum age for entries, in seconds - NOT IMPLEMENTED
MAX_ENTRIES_AGE = 3600

' Default value to be used, in percentage. We monitor the FREE SPACE, which must not go below the threshold.
' 1- when the attribute doesn't specify the threshold for a given disk
' 2- for all disks if there is no attribute AND DOWN_NO_ATTRIBUTE = True
' If set to 0, not specified disks will not be checked.
DEFAULT_THRESHOLD = 10

' Unit of default threshold - THIS IS NOT A DEFAULT UNIT FOR SPECIFIED THRESHOLDS
' "%" = percentage
' "G" = gigabyte
' "M" = megabyte
DEFAULT_THRESHOLD_UNIT = "%"

' %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

' Set the result code of the check (0=Success, 1=Error)
Context.SetResult 0, "No error"
bAlarm = false

' Retrieve DB object

Set oDb = Context.GetDB

If IsNull(oDb) Then
Context.SetResult 1, "Could not create DB object"
Else

' Fetch deviceID
nDeviceID = Context.GetProperty ("DeviceID")

' Get the attribute which contains the specific value.
sqlGetDS = "select sValue from DeviceAttribute where (nDeviceID = " & nDeviceID & ") and (sName = '" & THRESHOLDS_ATTRIBUTE & "')"
Set oRs1 = oDb.Execute(sqlGetDS)

' We report a DOWN if no attribute and script is configured as such.
If DOWN_NO_ATTRIBUTE and oRs1.EOF Then
Context.SetResult 1, "This monitor needs a attribute named " & THRESHOLDS_ATTRIBUTE & " to work."
Else
drvMonitors = null
If Not oRs1.EOF Then
oRs1.moveFirst
drvMonitors = split(oRs1("sValue"),";")
End If

' SQL request. We ask SQL to compute the value we want itself : it return the remaining percentage, megabytes and gigabytes on each disk.
sSql = "SELECT SDI.sDescription, SD.dPollTime, D.sDisplayName, (1 - SD.nUsed_Avg / SD.nSize) * 100 AS perc, (SD.nSize - SD.nUsed_Avg) / 1073741824 AS giga, (SD.nSize - SD.nUsed_Avg) / 1048576 AS mega FROM Device AS D INNER JOIN PivotStatisticalMonitorTypeToDevice AS PSM ON PSM.nDeviceID = D.nDeviceID INNER JOIN StatisticalDiskIdentification AS SDI ON SDI.nPivotStatisticalMonitorTypeToDeviceID = PSM.nPivotStatisticalMonitorTypeToDeviceID INNER JOIN StatisticalDisk AS SD ON SD.nStatisticalDiskIdentificationID = SDI.nStatisticalDiskIdentificationID WHERE D.nDeviceID = '" & nDeviceID & "' AND SD.dPollTime = (SELECT top 1 SD.dPollTime FROM Device AS D INNER JOIN PivotStatisticalMonitorTypeToDevice AS PSM ON PSM.nDeviceID = D.nDeviceID INNER JOIN StatisticalDiskIdentification AS SDI ON SDI.nPivotStatisticalMonitorTypeToDeviceID = PSM.nPivotStatisticalMonitorTypeToDeviceID INNER JOIN StatisticalDisk AS SD ON SD.nStatisticalDiskIdentificationID = SDI.nStatisticalDiskIdentificationID WHERE D.nDeviceID = '" & nDeviceID & "' ORDER BY SD.dPollTime DESC) ORDER BY SDI.sDescription"

Set oRs2 = oDb.Execute(sSql)
oRs2.moveFirst

While Not oRs2.EOF

' First we check if the last polled value is a recent one, if that check is enabled
' TODO

displayName = oRs2("sDisplayName")
description = ucase(oRs2("sDescription"))

'Default value
drvMonitorLimit = DEFAULT_THRESHOLD
drvMonitorUnit = DEFAULT_THRESHOLD_UNIT

' We retrieve the threshold from the attribute, if it exists.
If Not IsNull(drvMonitors) Then
For each drvMonitor in drvMonitors
'Is it a matching threshold ?
tokens = split(drvMonitor, "=")
If tokens(0) = description Then
' We then retrieve the threshold value AND the unit. The unit MUST be specified.
' Correct format is "100M", "10%", "4G" for example.
drvMonitorUnit = ucase(Right(tokens(1),1))
drvMonitorLimit = int(Left(tokens(1),len(tokens(1))-1))
Exit For
End If
Next
End If

Select Case drvMonitorUnit
Case "%"
value = int(oRs2("10"))
Case "G"
value = int(oRs2("giga"))
Case "M"
value = int(oRs2("mega"))
Case Else
' Invalid unit, we will report a Down.
value = -1
End Select

' If unit is invalid, it' a down.
If value = -1 Then
bAlarm = true
oChecksResult = oChecksResult & "Disk " & description & " : threshold unit is invalid (" & drvMonitorUnit & "). You MUST specify %, G or M as a threshold unit (example : C=10%;D=5G;E=650M)" & vbCrLf
Else
' If unit is valid, but threshold is zero, we don't check.
If drvMonitorLimit = 0 Then
oChecksResult = oChecksResult & "Disk " & description & " : " & Round(value) & drvMonitorUnit & _
" remaining space - not checked because threshold is zero." & vbCrLf
Else
' Else we check.
If value < drvMonitorLimit Then
bAlarm = true
oChecksResult = oChecksResult & "Disk " & description & " : " & Round(value) & drvMonitorUnit & _
" remaining space is below threshold (" & drvMonitorLimit & drvMonitorUnit & ") - DOWN !!" & vbCrLf
Else
oChecksResult = oChecksResult & "Disk " & description & " : " & Round(value) & drvMonitorUnit & _
" remaining space is above threshold (" & drvMonitorLimit & drvMonitorUnit & ") - UP" & vbCrLf
End If
End If
End If
oRs2.moveNext
Wend

' Store the result in an attribute. Allows to access details even on a Device-configured action by using the %Device.Attribute.* variable.

' Formatting it to a SQL compatible format.
if (Right(oChecksResult,1) = vbCrLf) Then
oChecksResultSQL = Replace(Left(oChecksResult,len(oChecksResult)-1), vbCrLf, "' + CHAR(10) + N'")
Else
oChecksResultSQL = Replace(oChecksResult, vbCrLf, "' + CHAR(10) + N'")
End If

' Checking if the attribute already exists. If not we create one, if yes we simply update it.
sqlCheck = "SELECT nDeviceAttributeID FROM DeviceAttribute WHERE (nDeviceID = " & nDeviceID & ") AND (sName = N'" & RESULT_ATTRIBUTE & "')"
Set oRs1 = oDb.Execute(sqlCheck)

' Storing it in DB as needed.
If oRs1.EOF Then
sqlStoreResult = "INSERT INTO DeviceAttribute (nDeviceID, sName, sValue) VALUES (" & _
nDeviceID & ", N'" & RESULT_ATTRIBUTE & "', N'" & oChecksResultSQL & "')"
Else
sqlStoreResult = "UPDATE DeviceAttribute SET sValue = N'" & oChecksResultSQL & _
"' WHERE (nDeviceID = " & nDeviceID & ") AND (sName = N'" & RESULT_ATTRIBUTE & "')"
End If
oDb.Execute(sqlStoreResult)

' Set the result of the monitor.
If bAlarm Then
oChecksResult = oChecksResult & vbCrLf & "Monitor is DOWN"
Context.SetResult 1, oChecksResult
Else
oChecksResult = oChecksResult & vbCrLf & "Monitor is UP"
Context.SetResult 0, oChecksResult
End If
End If
End If

' Cleanup code
Set oDb = Nothing
Set oRs2 = Nothing
Set oRs1 = Nothing

RE: Logical Disk Counters--What's wrong?

MB - NS — Fri, 23 May 2008 04:34:41 GMT

Could you post the script you're using ?

RE: Logical Disk Counters--What's wrong?

nickcarbone — Thu, 22 May 2008 13:20:19 GMT

Yes, the Disk Utilization performance monitor is enabled and I can see data in the report. Also, we are running version 11.

RE: Logical Disk Counters--What's wrong?

MB - NS — Thu, 22 May 2008 04:32:58 GMT

It means there is no samples in the DB.
Did you enable Disk Utilization performance monitor ? If yes, do you have data in the report ?
Also, this script has been tested only on WUG11, not on WUG12. It might not work on WUG12.

RE: Logical Disk Counters--What's wrong?

nickcarbone — Wed, 21 May 2008 20:19:05 GMT

[quote][b]MB - NS (2/8/2008)[/b][hr][quote][b]BobInDaNoc (2/8/2008)[/b][hr]I've considered setting up SNMP based monitors for the WMI ones that are failing, however it didn't seem as straightforward. The particular WMI monitor that I'm using, %free disk space, per volume, returns a % value that I can easily set a range for. I notice in SNMP mib, there's Bytes total, and bytes available, which would actually require a calculation be made, right, via a script? I didn't see, directly a way to check the free space % via snmp. If you've worked this particular issue out with a script, please share... I do like SNMP, certainly a more direct route into the data, without hardly much of an authentication system....

Bob[/quote]
There are some scripts around which use directly the values retrieved by the Disk Utilization perf monitors.

The one I wrote also allows you to specify the thresholds using the device attributes (enclosed in this post). This way you avoid having multiple monitors depending on the letters and thresholds you need. Please note that you need to have 'disk Utilization' enabled and working on the device.[/quote]

After applying the script i get the following error message when testing it against a server.

Error: Source:'ADODB.Recordset'
Line:77 Char:2
Error:0 'Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.'
-v
(null)

Any ideas?

RE: Logical Disk Counters--What's wrong?

kar98ghost — Tue, 13 May 2008 03:38:25 GMT

Somebody Help me in another topic ( really thanks to him ) fo memory utilization, i adapt the script for Cpu Utilisation.

The script turn the monitor down if the value of physical Memory is higher than 90% ( or another value ) during 3 hours ( you can easily change this value too ) .
So it can avoid the device to get down if memory is used during few minutes.
It work similary for CPU, if you have many cores, it take the average of utilization of all cores

For The cpu
_{// Set the result code of the check (0=Success, 1=Error)
Context.SetResult( 0, "No error");

// WUP Database connect
var oDb = Context.GetDB;

if (null == oDb) {
result = false;
err += "WUP DB inaccessible! ";
} else {
Context.LogMessage("DB OK");

// Get DeviceID
var deviceID = Context.GetProperty("DeviceID");

// Get the Percentage (3H average to maximum) for check
var sSql = "SELECT nProcessorLoad_Avg AS Perc FROM StatisticalCPU SM JOIN StatisticalCPUIdentification SMI ON SM.nStatisticalCPUIdentificationID = SMI.nStatisticalCPUIdentificationID JOIN PivotStatisticalMonitorTypeToDevice SMT ON SMI.nPivotStatisticalMonitorTypeToDeviceID = SMT.nPivotStatisticalMonitorTypeToDeviceID WHERE dPollTime > DATEADD(hh,-3,GETDATE()) AND nDeviceID = '"+deviceID+"'";
var rs = oDb.Execute(sSql);
var perc = rs("Perc")+0;
var perc = perc/100

Context.LogMessage("Perc: "+perc);

rs.Close();
oDb.Close();
}

// Set result Code
if (perc > 0.8) {
Context.SetResult( 1, "The average utilisation during the last 3 hours was greater than 90%");
} else {
Context.SetResult( 0, "Utilisation Ok");}

For the Memory (only physical )

// Set the result code of the check (0=Success, 1=Error)
Context.SetResult( 0, "No error");

// WUP Database connect
var oDb = Context.GetDB;

if (null == oDb) {
result = false;
err += "WUP DB inaccessible! ";
} else {
Context.LogMessage("DB OK");

// Get DeviceID
var deviceID = Context.GetProperty("DeviceID");

// Get the Percentage (3H average to maximum) for check
var sSql = "SELECT Round(AVG(nUsed_Max),0) / nSize AS Perc FROM StatisticalMemory SM JOIN StatisticalMemoryIdentification SMI ON SM.nStatisticalMemoryIdentificationID = SMI.nStatisticalMemoryIdentificationID JOIN PivotStatisticalMonitorTypeToDevice SMT ON SMI.nPivotStatisticalMonitorTypeToDeviceID = SMT.nPivotStatisticalMonitorTypeToDeviceID WHERE dPollTime > DATEADD(hh,-3,GETDATE()) AND sType = 'RAM' AND nDeviceID = '"+deviceID+"' GROUP BY nSize";
var rs = oDb.Execute(sSql);
var perc = rs("Perc")+0;

Context.LogMessage("Perc: "+perc);

rs.Close();
oDb.Close();
}

// Set result Code
if (perc > 0.7) {
Context.SetResult( 1, "The average utilisation during the last 3 hours was greater than 90%");
} else {
Context.SetResult( 0, "Utilisation Ok");
}

Hope it can be useful to someone

RE: Logical Disk Counters--What's wrong?

rhugh — Mon, 12 May 2008 10:58:40 GMT

[quote][b]MB - NS (5/12/2008)[/b][hr][quote][b]kar98ghost (5/5/2008)[/b][hr]
Context.LogMessage( " Hello ");

Where could i see the information send??? I start the nmeventviewer ( in Ipswitch/what's up gold/eventviewer.exe ) and i connect to ip where what's up is running ( it's my local computer )
[/quote]

AFAIK, you can only see it in the Test ox, but you may be able to see it in the WUG Event viewer, if debug is turned on.

For your first question about how to include the text in a email :
1- either you use an Active Monitor at the monitor level, and you can use the variable %ActiveMonitor.Payload (you should see the string provided in the Context.SetResult method in your script).
2- OR you insert the result in a device attribute, as I do in my disk script, and use the %device.attribute. variable. The advantage being that you can apply the action at the device-level.

BTW, the script output you posted seems like a custom memory script. Did you adapt the disk script in order to check for memory ? If yes, is it possible you share it on this forum ? I think it might interest some people.
[/quote]

I have a script for checking the physical memory using WMI as a Custom Performance Monitor, but the property CredWindows:Password does not work properly. I have to hard-code it into the script. I'm hoping WUP 12 fixes that issue.

RE: Logical Disk Counters--What's wrong?

MB - NS — Mon, 12 May 2008 04:50:44 GMT

[quote][b]kar98ghost (5/5/2008)[/b][hr]
Context.LogMessage( " Hello ");

Where could i see the information send??? I start the nmeventviewer ( in Ipswitch/what's up gold/eventviewer.exe ) and i connect to ip where what's up is running ( it's my local computer )
[/quote]

AFAIK, you can only see it in the Test ox, but you may be able to see it in the WUG Event viewer, if debug is turned on.

For your first question about how to include the text in a email :
1- either you use an Active Monitor at the monitor level, and you can use the variable %ActiveMonitor.Payload (you should see the string provided in the Context.SetResult method in your script).
2- OR you insert the result in a device attribute, as I do in my disk script, and use the %device.attribute. variable. The advantage being that you can apply the action at the device-level.

BTW, the script output you posted seems like a custom memory script. Did you adapt the disk script in order to check for memory ? If yes, is it possible you share it on this forum ? I think it might interest some people.

RE: Logical Disk Counters--What's wrong?

rhugh — Mon, 05 May 2008 09:39:29 GMT

[quote][b]kar98ghost (5/5/2008)[/b][hr]Hi all

I try to get the informartion i describe on the last post with the event viewer.
To do this, i use this command type :

Context.LogMessage( " Hello ");

Where could i see the information send??? I start the nmeventviewer ( in Ipswitch/what's up gold/eventviewer.exe ) and i connect to ip where what's up is running ( it's my local computer )

I see information in the event viewer, but nothing about the test i want, and information i get is about state change or id change.

Someone could help me???

thanks[/quote]

Did you remember to turn on the debug mode? You can do that by right-clicking in the event viewer, then going down to the "Debug On" line and left-clicking on it.

RE: Logical Disk Counters--What's wrong?

kar98ghost — Mon, 05 May 2008 04:41:52 GMT

Hi all

I try to get the informartion i describe on the last post with the event viewer.
To do this, i use this command type :

Context.LogMessage( " Hello ");

Where could i see the information send??? I start the nmeventviewer ( in Ipswitch/what's up gold/eventviewer.exe ) and i connect to ip where what's up is running ( it's my local computer )

I see information in the event viewer, but nothing about the test i want, and information i get is about state change or id change.

Someone could help me???

thanks

RE: Logical Disk Counters--What's wrong?

kar98ghost — Wed, 30 Apr 2008 04:54:46 GMT

My script Works Well, and i've another question I ever ask on the forum about another subject :

I set the value of maximum memory used to 10%, so the monitor is down. When i use the test function, it tell me this :

"Failure: Memory Physical Memory is 82 % full | Memory Virtual Memory is 29 % full | "

It's really an interressant information, is there any way to get it for example on a mail, orin a report Log and no just in this test function???

When i set the value ton 90%, it return me : Ok

thanks for your help

RE: Logical Disk Counters--What's wrong?

kar98ghost — Wed, 30 Apr 2008 04:32:42 GMT

ooh thanks
I tried to open the database with sql server and many other way ..... i just have to gon on the website... thanks a lot

RE: Logical Disk Counters--What's wrong?

MB - NS — Wed, 30 Apr 2008 04:27:43 GMT

[quote][b]KvChaos (3/19/2008)[/b][hr]Maybe a bit out of point, but is there a smiliar script for Processor counter as well?

And good job for this Logical Disk COunter script. It works great.. finally.:D[/quote]

No, there is not (or at least, I didn't wrote one, and I don't know of another one).

[quote]Hi

I don't know where you found the sql value to make the script????

I want to do the same for the memory usage and CPU, but i don't know where you got the name of variable.

Thanks for your script[/quote]

I used the DB schema, available there :
[url]http://www.ipswitch.com/support/whatsup/index.asp[/url]

RE: Logical Disk Counters--What's wrong?

kar98ghost — Wed, 30 Apr 2008 03:38:33 GMT

Hi

I don't know where you found the sql value to make the script????

I want to do the same for the memory usage and CPU, but i don't know where you got the name of variable.

Thanks for your script

RE: Logical Disk Counters--What's wrong?

KvChaos — Wed, 19 Mar 2008 22:27:37 GMT

Maybe a bit out of point, but is there a smiliar script for Processor counter as well?

And good job for this Logical Disk COunter script. It works great.. finally.:D

RE: Logical Disk Counters--What's wrong?

MB - NS — Tue, 18 Mar 2008 04:42:04 GMT

[quote][b]KvChaos (3/18/2008)[/b][hr]
However, I have some error setting the value for the attribute.
For example, when I put C=20% the test results still give me the default threshold which is 10%.
Did I put in a wrong format or something?

EDIT:I got amuch worstresult when trying to activate this script on a server with multiple drives. Nowwhen I test it, the script keep prompting for a Disk_Space_Thresholds, even after I added in the attribute.[/quote]

For the letter you need to put the exact drive name, as it is reported by the snmp agent (you can see it in the Disk Utilization report).

For Windows drive it's "C:\", "D:\", and so on.

So the attribute should look like this :
C:\=20%

I updated the comments in the script, as it's not easy to figure out.

As for your issue with another server, I'm not sure.
Make sure you spelled the attribute name correctly, and check that you don't have 2 devices with the same IP address (if that's the case, WUG mixes up the device ID, which is used in the script to retrieve the attribute).

RE: Logical Disk Counters--What's wrong?

KvChaos — Tue, 18 Mar 2008 01:20:02 GMT

I see..

However, I have some error setting the value for the attribute.
For example, when I put C=20% the test results still give me the default threshold which is 10%.
Did I put in a wrong format or something?

EDIT: I got a much worst result when trying to activate this script on a server with multiple drives. Now when I test it, the script keep prompting for a Disk_Space_Thresholds, even after I added in the attribute.

RE: Logical Disk Counters--What's wrong?

MB - NS — Thu, 13 Mar 2008 05:11:01 GMT

Configure the attribute in the device properties.

RE: Logical Disk Counters--What's wrong?

KvChaos — Thu, 13 Mar 2008 01:02:38 GMT

So how can I go about creating a Disk_Space_Threshold on a device?

RE: Logical Disk Counters--What's wrong?

MB - NS — Wed, 12 Mar 2008 06:30:55 GMT

[quote][b]jfreswick (3/11/2008)[/b]
What device attributes are enclosed in this post, I am attempting to set this up and am unable to find the SNMP Reference Variables to use... am I wrong in my assumption that this is an Active Script PerfMon?

Thanks[/quote]

It's an ActiveMonitor.
What is enclosed in the post is the [i]script[/i].

[quote][b]KvChaos (3/11/2008)[/b][hr]I tried testing the script,
but it keeps saying need "Disk_Space_Threshold" for it to work.

I have enabled Disk Utilization, and also added in the drvMonitors=null in the first line of the script.
Still it doesn't work. How so??[/quote]

I updated the script in the post yesterday so people don't have to add the line.
And yes, it needs you to create the "Disk_Space_Threshold" [i]device attribute[/i] on the device.

I set it this way by default so that people have to intentionally set the thresholds (they can still leave the attribute blank if they want to keep the default values, but it will be knowingly).

You can also set it so that it doesn't need the attribute, by setting the below value at the beginning of the script.

[quote]' If the threshold attribute is not found, should the monitor report as DOWN ?
' If set to False, it will use the default value for all disks.
DOWN_NO_ATTRIBUTE = true[/quote]

The script is commented (I believe quite clearly), so that one can use and tune it easily. Please read the comments in the script before posting there !

RE: Logical Disk Counters--What's wrong?

KvChaos — Tue, 11 Mar 2008 23:01:47 GMT

I tried testing the script,
but it keeps saying need "Disk_Space_Threshold" for it to work.

I have enabled Disk Utilization, and also added in the drvMonitors=null in the first line of the script.
Still it doesn't work. How so??

RE: Logical Disk Counters--What's wrong?

jfreswick — Tue, 11 Mar 2008 17:48:22 GMT

[quote]There are some scripts around which use directly the values retrieved by the Disk Utilization perf monitors.

The one I wrote also allows you to specify the thresholds using the device attributes (enclosed in this post). This way you avoid having multiple monitors depending on the letters and thresholds you need. Please note that you need to have 'disk Utilization' enabled and working on the device.[/quote]

What device attributes are enclosed in this post, I am attempting to set this up and am unable to find the SNMP Reference Variables to use... am I wrong in my assumption that this is an Active Script PerfMon?

Thanks

RE: Logical Disk Counters--What's wrong?

MB - NS — Mon, 10 Mar 2008 10:11:10 GMT

Ok, thanks for the information ! I'll update it.
Strange I didn't ran into it during my tests though...

RE: Logical Disk Counters--What's wrong?

arjan — Sun, 09 Mar 2008 10:58:40 GMT

Hi,

Great script - works like a charm.
Except, seems it doesn't work properly when the Disk_Space_Thresholds is not explicitly defined. In that case it gives a runtime error that the object (drvMonitors) is not part of a collection...

Defining it ("drvMonitors=null" before line 66) solves that ;)

KR,
Arjan

RE: Logical Disk Counters--What's wrong?

MB - NS — Fri, 08 Feb 2008 09:37:49 GMT

[quote][b]BobInDaNoc (2/8/2008)[/b][hr]I've considered setting up SNMP based monitors for the WMI ones that are failing, however it didn't seem as straightforward. The particular WMI monitor that I'm using, %free disk space, per volume, returns a % value that I can easily set a range for. I notice in SNMP mib, there's Bytes total, and bytes available, which would actually require a calculation be made, right, via a script? I didn't see, directly a way to check the free space % via snmp. If you've worked this particular issue out with a script, please share... I do like SNMP, certainly a more direct route into the data, without hardly much of an authentication system....

Bob[/quote]
There are some scripts around which use directly the values retrieved by the Disk Utilization perf monitors.

The one I wrote also allows you to specify the thresholds using the device attributes (enclosed in this post). This way you avoid having multiple monitors depending on the letters and thresholds you need. Please note that you need to have 'disk Utilization' enabled and working on the device.

RE: Logical Disk Counters--What's wrong?

BobInDaNoc — Fri, 08 Feb 2008 09:06:31 GMT

Leo!!!!!

WMIADAP /F made the logical disk counters available on at least one of the servers in question!!! Man, thanks a million! I'm going to run throught the other boxes to see if it fixes them up as well.

Thanks!

Bob

RE: Logical Disk Counters--What's wrong?

BobInDaNoc — Fri, 08 Feb 2008 09:00:58 GMT

I will try the WMIADAP command to see if that helps. The diskperf isn't an issue, these are always 2k3 servers, which have logical counters available on demand. Just in case, though, yep, I ran diskperf -Y and diskperf -YV, and rebooted. No luck, although I wasn't expecting diskperf -y to actually work :)

I'll check that wmiadap right away, fingers crossed...

Thx,

Bob