Hi All,
For few of my devices where we need Hardware monitoring to be functioning, I am getting the below error and the status remains as un-defined..
Hardware polling failed: ProviderModule is Disabled Scope
So any clue as to why this is happening?
NOte: Most if these are IBM servers..,
I'm trying to create an alert using the BizTalk Server 2010-2013 Message Box and Orchestrations Performance Counters template found here: BizTalk Server 2010-2013 Message Box and Orchestrations Performance Counters and I am having no luck being able to set the alert to use any of the components listed therein. It's just not able to see them. Is there anything I could be missing?
Thanks!
I am aware that SolarWinds requires 3rd party software to send text messages. Has anyone successfully sent an e-mail to the carrier and have it converted to a text message? For example: 1235558000@carrier.com
I have tried and haven't been able to get it successfully send anything and wondering if it is limitations with SolarWinds or somewhere else on the network.
Dears,
I am facing the subject mentioned issue while retesting the SNMP.
However, i just added few nodes successfully but when i tried to change the community string on recently added nodes, it gave me the error (see the attached snap shot).
After that i checked some random nodes to verify if the issue is with recently added nodes or with all the nodes, i found the same issue with all the nodes.
kindly help me to sort out this issue. Thanks -
Has anyone else had issues with agents following an upgrade to SAM 6.2.3?
One particular install I've been working on went from SAM 6.2.1 and NCM 7.4 to SAM 6.2.3 and NCM 7.4.1, then we put NPM 11.5.3 on top of that. The install seemed to go fine, no errors during the Config Wizard, and the web console loaded fine after each install. Things went downhill from there:
I presume the agent version would be the same regardless of which module I upgraded above as they were all released same day.
Currently have a case open with SolarWinds support but thought I'd post this while waiting for an AE. Case # 934710.
We will give support a bit of time to analyse and hopefully come up with a fix/solution but we have a database backup and server snapshot we can roll back to if it doesn't look likely.
Hi all,
Does anyone else get this issue where, after carrying out some function in Alert Manager, the page refreshes and greys out whilst it re-loads (shows the loading dialog).
However, after it completes and before you can highlight or click another element, the page greys out again and reloads once more, and this continues ad infinitum.
I'm using Google Chrome Version 54.0.2840.71 m browser, and the following Orion modules.
Orion Platform 2016.1.5300
IPAM 4.3.2
NCM 7.5
NPM 12.0
DPA 10.0.1
QoE 2.1.0
NTA 4.2.0
IVIM 2.1.2
SAM 6.2.4
NetPath 1.0
Thanks.
I have seen template for Hadoop integration with JMX is it possible to integrate Solarwinds with ClouderaI(CDH) and Hortonworks distributions for Hadoop monitoring using Cloudera manager and Ambari REST API?
Has anyone experienced an issue with polling engine CPU utilization after installing SAM 6.3 Hotfix 1? Since installing hotfix 1 2 weeks ago we have been experiencing issues with our additional polling engines. What is happening is CPU utilization on the polling engine servers are pegging out at 100%. The culprit appears to be associated with the SWJobEngineWorker2x64 process. If I kill the process CPU utilization returns to normal. But at some point after that the process will again max out the CPU. On one of my pollers, and as test, I uninstalled hotfix 1 and since doing so I have not seen the issue return. I'm now experiencing the issue on another one of my polling engines. Just wondering is anyone else has seen this same issue.
Guess I may just have to resort to uninstalling hotfix 1 from my primary SAM server and all additional polling engine servers.
Appreciate any feedback
Thanks in advance
Can someone help me as i am not able to fetch the SQL agent job info via AppInsight for sql.
Error - 'No valid data was received. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated'
I tried couple of things but that didnt worked.
1. Increased the timeout period for the whole template and the job info component.
2. Re - applied the template.
3. Checked the User account permissions( ran the sql query to fetch the job details on SQL management studio - that worked).
Anything, anyone can suggest?
Thanks!
We have a nice tool within Solarwinds to genereate reports with no indication of where the data is stored.
So we end up using a per database view within appinsight for SQL to export the data one counter at a time, one database at a time, one instance at a time to attempt to have an overall view. This makes no sense...
I'd like ot be able to extract everything at once but I can't correlate what I have on screen with what is contained in the database... There is no relationship defined at the database level which makes it impossible to output the database diagram. The entity model seems to be entirely textual with no diagram or research capabilities. And the descriptions are not that helpfull when stating that: components contains components, evidences contains evidences and statistics contains statistics...
I found the concept of 'Average Read Latency' and 'Average Disk sec/Read' per database in the apm_component but I cannot figure ou where the historical values are stored.
If anybody knows where the those information are stored, it would be appreciated. Or a simple way to figuring out where information is stored when a statistic is displayed on screen...
I am not sure if anyone has already addressed this or not. If yes, please let me know and I will remove this question.
My question is about end-to-end monitoring issues for tomcat and JVM monitoring.
We are using SAM and have setup the template but immediately receive errors of the components being down.
We believe the issue is because of the F5 Load balancer.
Does anyone have any information, examples, or can provide assistance in getting this resolved? Also, any experience in GuideWire?
Through JMeter scripts we are running tests on a new environment (GuideWire) and would like SAM to provide metrics for the following:
Any information and assistance is appreciated as this is scratching the surface for things to come.
Thank you!
We’re looking to provide more insight into your Amazon Web Services (AWS) environment. But first, we need to know a little about what you’re dealing with.
Please note that you may receive a follow-up email/PM from me – I might have a few questions to throw at you.
Feel free to provide any additional information you think we need to know in the comments section!
Hi,
We are having NPM, SAM, NCM in our Solarwinds. We have enabled Hardware Health Monitoring as well. But for the below Hardware Polling related warnings displayed on the device properties are not being triggered as an alert. Please help us, how to trigger the below mentioned warnings.
On a Windows server properties in Soalrwinds, we get the below warnings
1. Hardware polling failed: Polling job finished with 'Cancelled' state<- this has been shown under Node Status
2. 'Overall Hardware Status' has state: Could Not Poll<-- This has been shown under Hardware Details
The below error has shown for an ESX Server.
So, basically, we need an alert should be generated when hardware could not poll or fail. Appreciate the quick response.
Hi All,
Is there a standard report that would export each of the systems and what monitoring is currently applied to each system? if not has anyone done this before ?
thanks
Hans
I would like to create various dashboards/views and be able to display them on monitors around the office, but not have the console log out after a set time. Is this possible?
Good morning everyone,
This morning, I was able to successfully configure heartbeat monitors for a SaaS alert delegation platform named OpsGenie. Heartbeat monitoring will inform users in the assigned escalation schedule(s) that OpsGenie has lost connectivity to the Solarwinds server(s).
We previously used AlertCentral at my place of employment, only to find it wasn't top-of-the-line for our alert delegation needs. Also, modems were somewhat out of the question (management decision?), so we didn't really have much of a way to alert pagerholders if our entire network environment went down; or if our virtual cluster hosting the Solarwinds servers also went down. Since we're using Office365, we completely rely on Internet connectivity. If the primary and secondary Internet connections at our main site went down simultaneously, no Solarwinds alerts could integrate with OpsGenie to be delegated to the correct teams. We wouldn't even know about it! As you most likely already realize, many gaps existed for alerting.
My thoughts are that I should create a document that defines this simple process so that any other Thwack members utilizing OpsGenie can be led in the right direction. Again, this process is fairly simple and easy to learn how to do; but sometimes, it's best to have a fish given to you even if you already know how to fish.
Step 1:
Create a Heartbeat integration within OpsGenie. Ensure that the correct teams and recipients are defined. Also, copy the apikey because you'll need it later in Step 4.
Step 2:
Create a heartbeat name in the "Heartbeats" tab on the left-hand pane. I had to create two different heartbeat names for each of my Solarwinds front end servers (i.e. SAMserver, NPMserver). Make sure that "10 Minutes" is the defined time variable.
Step 3:
Download the lamp application ( Download lampzip - OpsGenie ). Unzip the file. Store the contents of the "lamp" folder on any disk drive of your Solarwinds server(s). (i.e. C:\Lamp)
Step 4:
Modify the lamp.conf file with the correct apikey. The correct apikey is provided in the initial Heartbeat integration created in Step 1 above. lamp.conf is located at <install path>\conf\lamp.conf (i.e. C:\Lamp\conf\lamp.conf).
Step 5:
Create a batch file that will execute the command necessary to properly send a heartbeat message from your server to OpsGenie. The command to be used is: lamp heartbeat --name <HeartbeatNameFromStep2> (i.e. lamp heartbeat --name SAMserver).
Step 6:
Create a scheduled Windows task on your Solarwinds server(s) that will run the batch file every ten minutes for an indefinite time period. This ensures OpsGenie will receive a heartbeat message once every ten minutes.
*NOTE: you will need to start the batch file in the install path of the Lamp application (i.e. C:\Lamp) or else it will not work as desired.
Step 7:
Review the heartbeat to ensure it is actively updating itself every ten minutes.
I sincerely hope the viewers of this document find the information helpful. Thanks all!
-Michael