Comments
-
Ahh just saw I renamed the column -- sorry about that , it's actually 'Current Numeric Value' when looking for it. EDIT: That or 'Current Value'. I believe depending on how you want to see the data. Current Value may look better and be more NOC friendly.
-
You would need to configure snmp on the windows machine, and change the polling method afterwards. Another option is deploying the SolarWinds agent on it.
-
You need to remove the 'SELECT Nodes.NodeID, Nodes.Caption FROM Nodes' part. The custom SQL query puts that part in automagically and doesn't let you change it.
-
You can also alert if the group goes into warning status as well. Though, I understand your need. I can't think of any way to currently do that unless utilizing a custom SQL, or SWQL query. If you adjust your alerts to use custom properties for email, I think that'd be the easiest way to achieve this. Rather than alert on…
-
I can't comment about the SQL Custom Resource as I have not used that before, but for limitations you can either put a limit on the entire view, or put a limit on a per-user basis. The end-result is the same, but doing it per-user might help you out a little more. That said -- I don't believe there's a way just to limit…
-
Use the 'Insert Variable' to help you get the appropriate variable names for this but to display the node name I believe it's ${Nodename} Always good to double check these by using 'Insert Variable' Did you get the alert to trigger as you expected? If not it would be helpful to put a screenshot of your alert scope and…
-
I don't have confirmation yet - but my gut says to me this is an Arista bug. To manually validate the SNMP data received for Arista, here's the OIDs nicely bundled into an article from SolarWinds :…
-
I had this happen once and turns out the SolarWinds log *.ldf file from the database was in need of more space. The volume in which the database held that file was out of space because the file grew so drastically. This was an extreme scenario though where massive edits etc. had happened prior. Certainly would want to hear…
-
From what I understood from the post, is that each SolarWinds server that is going to be part of the pool is given an additional network interface with an IP subnet of your choosing. This subnet would not route, or have connectivity, and the 'shared' IP is also in that shared non-routed subnet. It's simply to get around…
-
Yes you just use the radio button on the left-hand side to multi-select the subnets you want to edit, then click the edit button.
-
All the various options are documented here, https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-agent-migration.htm Hope this helps!
-
An interesting spin on that, the SWIS API exposes additional options not available when creating the property in the UI. Namely being able to define a default value. If interested you can read up. https://github.com/solarwinds/OrionSDK/wiki/Managing-Custom-Properties…
-
Are you pointing the configuration wizard at the availability group listener that you have setup in SQL server? There's no need for a driver, if there is... SolarWinds handles it for you.. I've never needed to worry about that ever in a new deployment. Might help to read up on AG's...…
-
If you're referencing an alert on an application, here's the variables that you would need for the nodes caption, and applications name, respectively. Node Caption: ${N=SwisEntity;M=Node.Caption} Application Name: ${N=SwisEntity;M=ApplicationAlert.ApplicationName}
-
I think that's a very unique edge-case @"mgaciarz". In some ways it may make sense that if dns lookups fail it consider the node down, but may be extreme to generally do that as dns can fail. I have no idea if SolarWinds tracks these failed lookups though with an event or otherwise. If it changes, that's an event but not…
-
Here's a couple success center links that detail some of this issue out (if it is the time zone mismatch). Also... were any services restarted after the timezones changes? They may not have taken effect yet if they do / should match now.…
-
Do you know if it’s the issue? Where did you get lead to that - just curious. If your transaction log is full it will cause all sorts of grief for you in your environment, logging in may be the least of the issues. Basically it will cause the database to seize up. I’ve always used the following sql query to check my…
-
I'd think the custom table should work, I don't think a Time-based data series is required (should be a way to remove that). Alternatively you could also possibly achieve the filtering with a view limitation. Maybe a custom swql query resource might be needed to get the level of functionality you're looking for.
-
Ok so that's not where it's stored - my bad. It's in the EngineProperties table but you'll need to query both tables anyway. Here's the different ways of getting at it and some examples. Note that there are other scale factors in the EngineProperties table -- may make sense to cumulate the results using this query but this…
-
Kudos! Now I'm thinking 'doh!' Much better for what bardeev is looking for. I've had to unfortunately use the queries to reference historical values.
-
Same here, naming convention is key -- couldn't agree more. Unfortunately nothing native to pull in the ActionID. There's no easy SWQL navigation properties to get at the ActionID. The issue really comes down to that fact that the Alert is the reference point and you can tie many upon many actions (in different escelation…
-
Have you opened a support case on this? If not get one open. Is the polling rate for the engine(s) exceeded and did you have stacked polling engine licenses prior to upgrade?
-
I used this exact method with a custom alert in DPA to alert if a table hasn’t been updated within a specified amount of time. Requires a bit more logic wrapped around it but that’s at the core of it and it works very well. Could easily be flipped the other way to check if it has an update too. DPA or SAM are the ideal…
-
While I mention this above... pretty sure official documentation (even if non-existent) would likely be to remove the existing groups or account and re-add them once they're changed so they take in the new SID and name. Thought worth mentioning.
-
Worth looking over the improvements specific to volume status in 2020.2 versions. Prior to 2020.2 versions yes... this is what’s needed essentially. Messy, not ideal, what have you... but yeah it works. In 2020.2 they introduced new volume status improvements and enhanced thresholds which makes for easier alerting on…
-
The configuration would need to be made at the devices sending the syslogs to alleviate the stress on the syslog server. Basically so less syslogs are actually being sent to this syslog server. Often people stand up multiple syslog servers to handle the extra load. The issue is that the syslog server (even if you make…
-
Flow data includes IP addresses. It looks like the query that you're posting is one of the auto-generated SWQL query alerts that NTA creates. In the SWQL table 'Orion.Netflow.FlowsByInterface', it has the SourceIP, and DestinationIP columns which you should be able to use to get what you need to adjust the alert for just a…
-
Specifically talking functionality, API Pollers are a functionality of SAM, and not NPM. I could stand corrected but I don't believe that's something they're working on integrating into NPM. https://documentation.solarwinds.com/en/Success_Center/SAM/Content/SAM-API-Poller-Licensing.htm…
-
If it's an API that's listening on tcp port 10080, and assuming it has a valid certificate provided by a real CA then you could use SAM's new API poller perhaps. All very good suggestions above though... I personally use NetPath all the time.
-
Just note Praveen, that isn't an all inclusive list. There are numerous devices that support sending flow data (in which I use myself) outside of that and are not mentioned. As HerrDoktor mentioned, worth checking with your network device vendor.