scottd

Comments

  • It is possible to work around cause we are doing it... You can build your alert complete the way you want it and then edit the Select statement in the AlertDefinitions table to read the correct way. this will make the alert function as it should. however, after you edit the Select statement manually and then edit the alert…
  • Sedmo, I think you got it... The logic is not flipped, just the syntax is written incorrectly.
  • Cool! They must have changed it along the way somewhere. Thanks!
  • Andy, This is how ours works. It seems to be working the logical way you described unless i am not understanding what you are saying... The SELECT statement generated for 'not all' taken from the db; SELECT Volumes.VolumeID AS NetObjectID, Volumes.FullName AS Name FROM Nodes INNER JOIN Volumes ON (Nodes.NodeID =…
  • Logically None should be NOT X or NOT Y or NOT Z. Not all should be NOT X and NOT Y and NOT Z This is exactly what i said 'None' uses 'or' and 'Not all' uses 'and'. And this is the way our implementation works. I have verified it by looking at the SELECT statements that gets written to the db. If i use 'none', an 'OR' will…
  • It has something to do with creating and dropping tables. I have always had is issue in report writer.
  • It takes 1 second to run from the SQL server here, otherwise it hanges in report writer.
  • The SQL would be; DELETE FROM Volumes WHERE VolumeType = 'Compact Disk' This will remove records with the volume type Compact Disk.
  • One more thing... You will also need to make sure that your Orion server computer account has administrative rights(member of the local admins group) to the server that the script runs on or else the script will never run. The orion server must authenticate to the server that the script will run on. The script creds come…
  • Very nice! Glad you got it sorted out. scott
    in Alert error Comment by scottd March 2010
  • John, The value you want to change here is, 1073741824. Solarwinds records these values in bytes so we divide that number by 1073741824 to return gigabytes. If you want to return the value in megabytes replace '1073741824' with '1048576'. You can also change the word 'Gigabytes' to 'Megabytes' if you like, but it doesnt…
  • The best way would be to not monitor them, thus removing them from the db, removing all chances of receiving an alert for a cdrom drive. Once you remove the resources, the cdroms will disappear from your Volumes table.
  • That looks like it should work. A sample of how we alert on windows disk volumes(the whole alert condition is not shown);
  • Here is the actual Select statement that runs. It looks good to me and the test alert i have setup is working as i think it should... I think if you fix that last condition to Percent Memory Used you should be fine. Unless i am not understanding your criteria completely... SELECT Nodes.NodeID AS NetObjectID, Nodes.Caption…
    in Alert error Comment by scottd March 2010
  • While I'm at it, I guess you could also replace the text 'almost' with; ${SQL:Select CAST( ${VolumePercentUsed} AS Decimal(18,0)) AS PercentUsed}% to get a percentage of how full the drive is. then your message would look something like; Volume C:\ on Server1 is 90% full and has 750MB available. Just another option and a…
  • Ooo! Also check your last condition... Are you looking for the Amount of memory used or Percent Memory used?? That line says Memory used is greater than 30 bytes.
    in Alert error Comment by scottd March 2010
  • That is strange... If the Id's are the same then that would confirm that the alert is firing twice for the same node. At this point i would probably create a new alert and scrap the old one and see if anything improves. I have not seen this exact behavior before, but have have seen some strange things happen with my…
  • Andy, It looks like 'none' translates into SQL as; NOT (Volumes.Caption LIKE '%c:\%') OR And 'not all' translates to NOT (Volumes.Caption LIKE '%c:\%') AND. The only difference being 'and' and 'or' which seems logical to me. Are you saying that this is not the intended functionality of 'none' and 'not all'. We have alerts…
  • I'm not a SQL guy at all, so I'm trying to make this work. I was able to get my alert to display in MB, but how did you get the 750 to round up to a whole number? There was no rounding function built in to that statement. I guess i just got lucky when a whole number popped in there. But if you want some some rounding done,…
  • You could just not monitor the cdrom drives... Do you have a need to monitor the cdrom drives? We have never monitored them as we have no need to. Maybe your business case is different...
  • Yeah, the basic alerts are very basic and intuitive to set up. But once you get used to using the advanced alerts, you will never look back to the basic ones again. The advanced alerts are so much more flexible.
  • duckstar, You dont really have to delete the entire node. You can delete the unknown interfaces on the node and then add the correct ones back in by listing the Node Details of the device and selecting them. This way you dont lose all of your node stats just the interface stats. We have the same issue here, and yes, we…
  • No problem. Glad you got it sorted out...
  • Let me check the DB to see what the actual select statement is reading. Gimme a few minutes...
    in Alert error Comment by scottd March 2010
  • Under 'Property to Monitor' tab, do you have 'Status' checked under 'Node Status'? And under 'Alert Trigger' tab, do you have the proper checkboxes filled in, according to your requirements?
  • MrSampsonite, Refer to this thread for your answer. scott
  • Did you check the tables in question after the maintenance run to verify the new retention policy was working correctly? Also, when records are deleted from the db, that doesnt always mean that the table space will be freed up. You may need to rebuild your indexes to reduce the size. If you have a DBA available to you,…
  • did the repeat alerts have the same AlertDefID?
  • Cool! Glad you got it sorted out...
  • dmc, Dump this into an Advanced SQL report and it should give you what your are looking for, space measured in GB's. I just used 'Fixed Disk' as my filtering criteria, but you can add more filtering to the 'Where' clause as you see fit. Select Nodes.Caption AS Node, Substring (Volumes.Caption,1,3) AS Volume,…