njoylif ✭✭✭✭✭

I could use a variation of this as well...

I just migrated my DB and primary polling engine to a new network (have several additional pollers and web servers). After migrating, I upgraded every module as we were a few minor revs behind. My suggestion: this assumes installing on new systems in new DC... take backup of your database (both if running NCM as well).…

verify your virus scan app is not blocking outbound emails (prevent email worm). I've been bitten several times by this.

try applying hotfix 1 if running 9.1 sp2. Strange it is only doing for your account though.

Interesting way to do it....try this: DECLARE @StartDate DATETIME, @EndDate DATETIME SET @StartDate = dateadd(day, -30, getdate()) SET @StartDate = dateadd(dd, datepart(dd, getdate())*-1, @StartDate) SET @EndDate = dateadd(day, 30, @StartDate)

wierd, maybe try < NOT(GroupStatus='Down') > or < GroupStatus not like '*Down*' >

hey have a bunch of AWESOME quick (5 min or less) tutorial videos online. Grab the one for the specific area you are focusing on. Great to get you started.

FYI - 2010.2.1 is the "Orion.Core" version. the NPM version should be to the right of that some. I also am having issues with the messages loading. If you open a ticket on it, please update this post as you go. Thanks much!

seconded!

the time in milliseconds it took for the polling engine this object is assigned to ping the object and the response to get back. i.e. ping response time from the poller to that node.

Rockin! thanks all

I would guess it is more of a load issue. I have remote connections (56k) that when traffic utilization is up the response time shoots up to 1500 ms or higher sometimes. It could also depend on the load of the 6509 itself... at least something to look at.

at least in the 10.x (and latest versions) there is a table in the database for AlertDefinitions and AlertActions. Verify they exist in your 9.x implementation and see what is in them. These should be safe during upgrades. Before doing any upgrade, I recommend you do a full backup of your database prior to upgrade. Run…

Hmmm, I'd try coping the report to a different name for testing. change the SQL to filter for ${Nodes.NodeID}...not sure best place to do this, on filter tab I would guess. to add to node details page, edit that view and add resource -> report writer -> report and select your new report.

I'm not clear on what you are trying to accomplish with the SQL queries...so you are using queries and not maps? I suppose you could write queries by site that do a true/false check on the device list for that site and propagate that maybe???

what version are you running? in 10.7 there doesn't appear to be an easy way to do this, since you have to select the map via list. the back end tables use the uniqueID for the "SelectedMapID"...don't know if it'd work to put map name.

 I grabbed them a little differently, but to the same result. I wrote a SQL query that copies from the Custom Poller Status table to my Nodes table in a customproperty field: UPDATE Nodes SET SerialNumber = s.Status FROM CustomPollerAssignment a JOIN CustomPollerStatus s ON…

try using HTML style or ANSI. I've actually gotten HTML tags to work in there, but sketchy at first.

HERE is the Feature Request submitted by jspanitz‌ - and don't forget to vote your own ideas up!

try adding at end of where clause: and virtualmachines.displayname NOT like '%<servername to exlude>%' edit - added NOT like (to exclude)

I'm wondering how to get the table back, like you could in the app version...I need to monitor physicalDisks on F5s and there are a mix of single and multiple drives.

Same as other thread:::there is a great PDF discussing advanced alerts and includes suppression. under Forum - Orion Family -> Alert Lab Here is link: 

I would open a case with support (and probably get on the phone right after to get an engineer working on it with you asap, if I were in your shoes.

not as straight forward as you might think... In simple fashion, yes, the app is ignorant of a LB in front. I have 3 AWEs behind a F5 LB. The rub I haven't been able to work around is the authentication piece. i.e. when I get LB'd to srvA, I have to auth with that server. when a request goes to srvB, I have to auth to srv…

I also have seen a delay, but not nearly as long. perhaps 15-30 seconds in NPM 9.5.

I'll try to spend some time on this tomorrow; what version are you running? in 12.0.x, there is a resource available that shows you what alerts could be triggered by that object...at least you could spot check until we get the report going.

I think the cleanest and most scaleable way is to use a custom property. I use "AlertEmail" and have a CP named this for all object types (node, apps, volumes, etc). then you can set on per node basis. for any emails that all alerts get sent to, use the DefaultEmailTo in SMTP settings

it has to match up. same for additional polling engines if you have them.

check the windows task scheduler (either in control panel or under admin tools).

ok, interesting. Thank you for responding. I'll take a look at that. Have a great day.