mrxinu

Essentially if a user contacts the helpdesk they want a monitor/query that says "Solarwinds confirms that you can send IMs". How is the user contacting the helpdesk? Are they messaging you? I'm trying to get a notion of what is supposed to trigger the "all is well with IMs" response.

There's a known issue in the discovery engine that's causing this. I ran a ticket with SolarWinds and they said it would be prohibitively difficult to resolve so I suppose it'll get sorted out during the next major revision, but no promises yet. You're right about the field types; it's actually getting truncated from the…

Hi there, I'm not sure what you're doing with the -4 math (time zone maybe?), but I've fixed the where clause so that it keeps your results between 00:00:00 and 23:59:59 yesterday: SELECT o.AlertObjectID AS Ticket_Number, o.AlertID, o.EntityCaption AS [Object], o.RelatedNodeCaption AS NodeName, n.IP_Address,…

You can use an SQL variable to get the drive letter only. Try putting this in the email message: ${SQL:Select Substring ('${Caption}',1,3)} That should convert 'C:\ Label:APPS cc18254b' to 'C:\'.

The submit button just confirms that you've chosen to change the previous polling intervals for new nodes being added going forward. The 're-apply' button goes back and updates all the existing nodes. So, if you don't mean to update all your existing nodes, just hit Submit and call it good.

Why not use the 'External Application' alert action to call osql to run the stored procedure?

Did you have a chance to read any of the examples I sent you? Have you been able to make those work at minimum?

I've never heard of it - where did you get it?

Without knowing why your existing solution is flawed I can't suggest a replacement - what's wrong with it?

I understand what you mean by login events - it has to SSH to the server to run the script, but what do you mean by clearing them from the tmp folder? The scripts that get copied over should be getting cleaned up on their own. Can you show us what the tmp directory looks like before you have to clean it up? -- Steven W.…

You could use the API to delete the nodes and interfaces you don't want if you can come up with a method for identifying them (e.g., all loopback interfaces). If you're interested in that I'll send a pull request to the SolarWinds OrionSDK repository for examples of both. -- Steven W. Klassen Programmer Analyst @ Loop1…

I don't know how dev savvy you're feeling, but WHD does have an API. You can create tickets using it: Web Help Desk REST API Guide

You can go into Settings > NCM Settings > Manage Policy Reports and then disable the report you no longer want running. -- Steven W. Klassen Programmer Analyst @ Loop1 Systems http://www.loop1systems.com/ http://www.linkedin.com/in/mrxinu

What would you consider a rapid rate?

You'll need to run the snap-in from the application server, but you're most of the way there already. Try this. Add-PSSnapin WebFarmSnapin $ready_for_load_balancing = (Get-Server -WebFarm WEBFARM1 -Address SERVER01A).ReadyForLoadBalancing # gets our true/false value Write-Host "Statistic: 0" # just write this out since…

You can use the regular HTTP monitor (as opposed to the HTTP Form Login monitor) for this. Set your credentials for the component and it'll handle logging into the pop-up authentication.

Rather than checking for a changed LastBoot you could use a custom poller to get HrSystemUptime instead. Updating your alert to check for a low value for that poller (if you're polling every 10m, check for a value <11m) would narrow the window a bit.

Ditto to what said above, but if your colleague is already gathering the information daily (and wouldn't mind doing it more often) you could dispense with trying to mirror the monitoring in SAM and just have him update a table in the SolarWinds database (of your creation, maybe named '_xenappfarmstatus') that you would…

So to be clear, what changed? It worked before you upgraded the DLL?

What products do you have?

A web-based report would do the trick: SELECT e.EventTime, e.MessageFROM Orion.Events eJOIN Orion.Nodes n ON e.NetObjectID = n.NodeID AND e.NetObjectType = 'N'WHERE n.Caption = 'ServerABC'AND e.EventType = 40 -- 40 = unmanage nodeAND HOUR(ToLocal(e.EventTime)) = 4AND MINUTE(ToLocal(e.EventTime)) <= 30

It might make sense for you to create a custom property called WAN of type Yes/No and set those particular interfaces to Yes so you can use that in your alert trigger condition: * Go to Settings. * Go to Manage Custom Properties. * Click Add Custom Property. * Change type to 'Interface'. * Set type to Yes/No. * Set your…

Happy happy to you too. =)

The only thing that comes to mind is changing the user that runs the alert service to something that has access to the remote system. At that point you shouldn't have to offer any credentials.

There's another thread you may be interested in that talks about a couple of ways to keep that directory clean. There's a batch file written by casperinmd and a powershell written by me. http://thwack.solarwinds.com/message/159893

It sounds like you may have found a bug. In the meantime, you could create a custom poller that retrieves hrStorageUsed (1.3.6.1.2.1.25.2.3.1.6) for your volumes. Once you have that information for each of your servers you could create a report against the information.

If you go into the user or group's account settings under Settings > Manage Accounts you can toggle these settings to no.

If you go into your NTA settings you should be able to uncheck interfaces you don't want any netflow from. If you're seeing more than the one interface you want it's because you're either getting netflow from it (with 'accept netflow on unmanaged interfaces' enabled) or the interface is selected as a netflow source in the…

Interesting - I didn't even know there was a verb for that. I need to review evidently. Where did the 'Dashbaordv2' bit come from? Was that in your .OrionMap file?

I hadn't heard that EOC & NPM couldn't be in different timezones, but it makes sense: the former is trying to aggregate information from the latter and needs to have a consistent time frame. What's the need for having them different? Maybe that's something we can work around with custom properties.