cahunt

4 starts to Five as the responses in this thread should be bookmarked by everyone.. valuable things here. Very valuable.

8Right off the bat it looks like you can adjust the top portion - all the Volume Type <> take more to process than = Nodes Custom Properties - b01_PrimaryPlatform - is equal to - Windows Volumes Custom Properties - v14_VolumeDisableAlerting - is equal to - 0 Volume - Volume Type - is not equal to - NetworkDisk * Volume -…

It's hard to tell you why an alert did not trigger without seeing the full alert details. If the issue was remedied before the required time frame to trigger then you may see the high point on a graph or the screen of the node, but no alert. Also if you go to Settings -> Orion Thresholds and Polling (section on settings…

If the Volume could not be reached it would incur a status change. The node, volume and any other entity should remain in the DB/system since it was not deleted and simply change status. graphs and charts would be affected for the entity, not the overall count of, or entities themselves. If you are on a VM and the label…

The node may have been moved, is there a message for the volume being added to another poller? If you put the events and/or audit events widget on the volume details page (if not already there) you should be able to see the full picture. It should also show on the node details page if it was moved from one poller to…

Indeed. I think I have found the block is great for monitoring status and inventory, thanks for the feedback cejay79! If you are able to mark anything helpful/useful it is always appreciated.

I would recommend taking out the Netflow FastBit DB IP from your Websites Table - If it shows there. That DB is setup for High IO and Web traffic may cause issues/delay which always have the possibility to implicate bigger issues or holes in data. I have not specifically experienced or seen anyone else with a setup like…

ALL YOUR RAM BELONG TO US! * I think this is their SOP when prepping leased machines to be sent back.

It's called a black hole... once you enter the office never get's you back.

Missing the Vineyard Blend in the PIC - but that's how I keep myself going from Play to Play Harder to Play the Hardest wake up and do it again! (my work is play, so you get it) * very possible I missed a round or 6 of play within my normal day

Nice to see someone found a good use of all those old Nat Geo's

Thanks. Regular residents at my desktop - no staging here, unless it's a Cisco Device.

And your alert conditions are? *Asking mainly due to noticing this is in NPM forum, but reference to a sql server could mean app or db issues depending*

So when you sync, are there nodes that meet alert conditions; or are the newly sync'ed nodes left out of the alert rotation to give you time to make sure everything is kosher?

That does work sometimes, but recently it has stopped being the remedy that brings them back to life. *besides I am tired of changing pollers and rediscovering nodes, when they have not changed

Nest the IP Addresses.... create another ANY condition to hold those ALL -> Condition; to tie these together (same building/other custom property, naming structure/sequence to tie to or the Node/Site Name since it should be the same) -- you may or may not need this additional condition to hone in on these two specific…

You got it! I'll post any updated versions here as well if I can figure it out.

Core.BusinessLayer.Log might have some correlating messages about(possibly before) that time of 11:01 PM. If you can find an associated msg with either a node ID, Name or IP it might point you to the device that did not respond so well. If the device is the issue you would more than likely see evidence in the device log…

It's a simple adjustment to your alert... Parentheses your initial argument and add an, AND CustomProp4Maintenance = True. And far easier than trying to create the Start End Date and Time maintenance fields that you then have to really go to sql alerts for, and an issue if not done correctly.

Interesting, So which Rogue alerts do you have enabled? And which ones specifically are coming through in these instances? MAC, IP, DNS? In any of these events do the MAC's end up being from the same device?

DB hang up, or a bad read.... either way something like that on my end gets a support case.

NPM will tell you if the node you are trying to add to the system is already being monitored. But it will not tell you that an IP is being used more than once on your network. Go syslogs for this.

Just ran a fresh install of Core 2019.2 HF1, NPM 12.5 and NTA 4.6 - getting the same error on those custom charts Specifically it looks like the queried (SWQL/SQL) resources, as the dynamic query builder is showing data just fine.

Your session trace should help uncover where the connection is being dropped. If you have only adjusted timeouts within Orion, consider adjusting the Timer Management Settings. Increasing the Close Wait or Time Wait so the F5 gives time for your Orion to respond may help. But Again the session trace will help uncover what…

The placement of your Servers and HA Servers will determine use of ether VIP or DNS update/cname. Cross sub nets you can not use a VIP, unless you have an OTV Network that the VIP can reside in and is properly routed So most cross domain/network setups will use the DNS update; and adjusting the IP Address on the virtual…

Understandable.

Yes Sir, I did double check and support for the Availability group listener is enabled with the LB in place. Regarding the servers, there is a 1 to 1 need/ratio (Primary/Secondary) services will be active from one of the two servers within each pair. You can choose which server should be active if there is a preference,…

Orion.AlertConfigurations There is an export verb available.

This would be fun, count me in.

You may be administrator - but does that account still have Node Management Rights? Or whatever account you are using - being admin you can view account rights or change accounts...edit the account you use and make sure Node Management is an option - even if so, re-save/submit the page and then try. *** Or check your DB to…