jagle

Is this still "on the list"? I'm not seeing any resolution for this.

So it would seem that "Top XX Endpoints|Conversations" aggregates ingress/egress. If you want to see true ingress/egress numbers you need to view "Top XX Receivers|Transmitters" (not the global one) resource on your NTA node details window. Still though the toggle seems to bring nothing to the table, am I wrong?

Awesome! That's 1.3.6.1.2.1.10.18.7.1.2 for T1 error seconds for anyone who searches this post. Thanks for your help!

After digging around I found another post that got around this in a clever way. It's sort of a SQL injection from the event log action. http://thwack.solarwinds.com/message/150221#150221 Still, why isn't this a feature of advanced alerting natively?! And why is "natively" not in this spell check app...seems like "changing"…

That caveat about a dedicated physical box for SQL is not mentioned on the site. Where the following quote comes from. -------------- "Orion NTA has matching system requirements to its host Orion Network Performance Monitor. Please refer to the Orion NPM system requirements for details." Operating SystemWindows 2003 Server…

**bump** I think I'm noticing the same thing on my NTA. In my experience, the ingress/egress toggle does not change the report that is displayed. I ran an NTA details for the last 8 hours on an edge router of ours just now. I compared the "ingress" with the "egress" and there are NO,not one or two, or a few, NO differences…

The reasons for the separate servers are unimportant, and EOC goes beyond what we need to support (the NCM and NPM instances monitor the same set of nodes). Bottom line, we need to bring these two instances together on one, preferably virtual, machine. With an external SQL server (if that is best practice).

Seems daft that you can influence custom properties in basic alerts but not in advanced alerts. Anyone know if this has changed, or might in the future? Zombie thread...

Thanks. That's very good, and most of what I'm looking for. I don't see a OID for errored seconds in there though. Anyone find that?

I dabbled in transforms as well. Since both servers use the same custom poller it just returns 2x that servers' current user count. I tried creating seperate custom pollers, but the result is the same. For example: {WestPoller}+{EastPoller} = 2x whichever server it is applied to, not East+West There is no way to reference…

I'm betting that you have your read-only string defined within NPM, but no read-write string. That's absolutely true. Although we've never defined one in NPM before, and never seen these logs. If true, wonder what it could be trying to do with r/w (if anything) on the switch? I think I'll just not log it, in lieu of…

Digging up this zombie thread... Ever get an answer to this one? I get this all the time, syslog is becoming unusable via the web console.

BTW, 5 Months later our database is only about 20 Gigs. So size seems to be pretty small despite cranking all the settings up and adding more nodes. We're also running the poller and the DB on separate virtual servers. Runs along perfectly, if a little CPU hungry.

"Bueller? ...Bueller? ...Bueller?" Magic 8-Ball says...200 GB any comments?