Hmm. Can I use the Orion SDK to update metrics directly? Or is it more for manipulating node data and metadata?
e.g. something conceptually like send-orionmetric -node X -metric Y -value Z
Hmm. Can I use the Orion SDK to update metrics directly? Or is it more for manipulating node data and metadata?
e.g. something conceptually like send-orionmetric -node X -metric Y -value Z
Cisco 2911/K9 is pretty egregiously incorrect.
Out of 311 of these routers in our system, 8 were assigned EOSupport 10/31/2016, EOSales 11/01/2011, OESWMaint 10/31/2014. No idea where it pulled those dates.
Two were matched to completely different devices:
The actual EOSupport is 12/31/2022: End-of-Sale and End-of-Life Announcement for the Cisco 2900 Series Integrated Services Routers - Cisco
If the feature can't be trusted to provide good data, it's no faster than compiling it by hand.
Trying to set maps 2.0 to be view able for all users and the box at the top that you check for all users is grayed out each time I come back to maps. How can I make sure it is saved and available for all users???
I am beginning to use the baseline management function in NCM 2019.4.
I have added 3 baselines to begin testing, and created an alert to notify me when the latest config does not match the current baseline.
However, the database baseline table shows mismatched lines, while the web console does not.
Anyone have an idea why?
Web console:
Database NCM baseline table, showing only 1 of the 3 matches with current config:
Found it. You must use the NCM_BaselineViolations, and trigger off of the IsViolation field. Don't know why this isn't an available out-of-the-box alert.
I'm using Solarwinds NCM 7.3 and I'm trying to create a job that will download configs and then set the newest config as baseline for a group of machines. Can anyone tell me if this is possible? I've setup groups in the web console, but the job creator doesn't see that group for some reason. Any insight is appreciated!
I'm trying to create an alert for orion to have a SWQL query to look at a volume's current rate of change and then if it notices a larger than average change to create an alert. I know this has been asked multiple times, however i was looking int what data i can access via the SWQL and think i found a different way to look at it where it might be worth looking again.
I have been able to get a consolidated average of the disk percent usage with the following query (may not be the most elegant but it gets the job done for now)
Select day, Avg(pcnt) over(partition by day order by day rows between 6 preceding and current row) as myavg
FROM (
SELECT DATETRUNC('Day',DateTime) as day, sum(PercentDiskUsed) as pcnt
FROM Orion.VolumeUsageHistory
Where VolumeID = '68'
Group By DateTime
)
Group by day
Order By day DESC
right now i have it hard coded to a specific volume to test. this is giving me the average volume side each day and also trucating the current data into a single point and finally is giving me one value as a singe day so I'm not messing with random time stamps.
Right now i cant figure out how to take this and figure out what the average change is over any period of time, be it to the first record or just say 30 days or a week.
If anyone has any ideas i would greatly appreciate it.
The settings option available under solarputty won't work. Although putty saves the font settings it doesn't get applied on the ssh session (it remains the same small size of 10) opened by solarputty.
I made an experiment and downloaded a msi putty installation file. I installed this putty package on the location where the putty called by solarputty is C:\Users\xxx\AppData\Roaming\Solar-PuTTY-v4\
Once I replaced with a brand new putty installation the font size started to reflects the size I set under settings BUT.... the solarputty stopped to work as expected. When you click on the session under solarputty a new putty window (outside of the solarputty window) opens and the credentials saved under solarputty fails. It successfully set the user id but the password field fails to fill up and you have to add it manually.
Conclusion: Something is wrong with how solarputty handle changes with the putty that comes with solarputty (don't know if it has to do wiht platform, mine is windows 10). Solarputty ignores the changes applied under putty. The workaround found (install putty over the putty that comes within the solarputty package) works for that font size/color setting but it takes away the functionality of opening sessions in tabs under solarputty windows and also takes away the functionality of the credentials saved under solarputty.
There's no good option for piping metric data directly into orion. The api *could* be used to do it, but the application as a whole would probably not be happy with you because it was designed with that kind of flow in mind. Orion assumes that they will be the ones collecting metrics, its not just a time series database receptacle like a prometheus or influxdb. They wrote the code for collecting data with the assumption that you would not need to do it yourself.
I have the same issue. Although putty saves the font settings it doesn't get applied on the ssh session (it remains the same small size of 10) opened by solarputty.
I made an experiment and downloaded a msi putty installation file. I installed this putty package on the location where the putty called by solarputty is C:\Users\xxx\AppData\Roaming\Solar-PuTTY-v4\
Once I replaced with a brand new putty installation the font size started to reflects the size I set under settings BUT.... the solarputty stopped to work as expected. When you click on the session under solarputty a new putty window (outside of the solarputty window) opens and the credentials saved under solarputty fails. It successfully set the user id but the password field fails to fill up and you have to add it manually.
Conclusion: Something is wrong with how solarputty handle changes with the putty that comes with solarputty (don't know if it has to do wiht platform, mine is windows 10). Solarputty ignores the changes applied under putty. The workaround found (install putty over the putty that comes within the solarputty package) works for that font size/color setting but it takes away the functionality of opening sessions in tabs under solarputty windows and also takes away the functionality of the credentials saved under solarputty.