Quantcast
Channel: THWACK: All Content - All Communities
Viewing all 19354 articles
Browse latest View live

Informations receive in alerts.

$
0
0

Guys,

when I receive a alerts  of the CPU Load, the results is  a negative Number For what ???


Need to be able to pull variable from a Cisco router and use that in a config change template

$
0
0

Good morning

 

I need to be able to pull the cisco router's default gateway address and use that to create a static route, ie

 

abc-de-01234-01#show ip route | inc resort

Gateway of last resort is 44.44.44.44 to network 0.0.0.0

 

Then use that 44.44.44.44

 

conf t

ip route 11.11.11.0 255.255.255.224 44.44.44.44

 

As part of a config change template.

 

Regards

Nigel

Group "Muted nodes" on "Manage Nodes" page

$
0
0

So, Solarwinds finally released the long awaited "Mute Alerts" feature in the last version

That's absolutely great, but there's an important feature that I feel should go hand in hand with it:

 

Add the ability to Group nodes by their "Is alert Muted" value, in the "Manage Nodes" page.

 

The Problem:

Currently, if you mute alerts for a number of nodes (let's say, for applying security patches and restarting part of your production servers whilst keeping your site live),

you have no easy way to view them all grouped together, in order to "un-mute" them when you're done, and you'd have to either look them up by name, or go through the whole list and its multiple pages.

 

The fact that the "unmute" indication is in the form of a comment following the node's status does not help...

Capture.PNG

 

The closest I got to this was sort by status, but as you can see - the actual status has got precedence (and so it should!),

and I would really like to have the option to just view all muted nodes in one go.

 

My Suggestion(s)

 

1. Grouping:

Would be great to have either another "Group By" option in the drop-down list, maybe something along the lines of "Is Muted".

 

2. Improve Visibility

It would also be nice to have a dedicated "led" state for this, so that muted nodes will pop out and will be easier and quicker to spot.

Maybe maintain the actual led color for the node's current status as it is, but add an "X" overlay (or anything else more self-explanatory...)

Fellow Thwack members - suggestions for this would be most welcome

 

* I've only given "Node" type entities as an example here,

but needless to say - this should apply also to "Manage Applications" in SAM and any other Orion product for that matter.

Troubleshooting: A Forcing Function on the IT Career Path

$
0
0

Troubleshooting efficiency and effectiveness are core to uncovering the root cause of incidents and bad events in any data center environment. In my previous post about the troubleshooting radius and the IT seagull, troubleshooting efficacy is the key performance indicator in fixing it fast. But troubleshooting is an avenue that IT pros dare not to walk too often for fear of being blamed for being incompetent or incorrect.

 

We still need to be right a lot more than we are wrong. Our profession does not give quarters when things go wrong. The blame game anyone? When I joined IT operations many a years ago, one of my first mentors gave me some sage advice from his own IT journey. It’s similar to the three envelope CEO story that many IT pros have heard before.

  1. When you run into your first major (if you can’t solve it, you’ll be fired) problem, open the first envelope. The first envelope’s message is easy – blame your predecessor.
  2. When you run into the second major problem, open the second envelope. Its message is simply – reorganize i.e. change something whether it’s your role or your team.
  3. When you run into the third major problem, open the third envelope. Its message is to prepare three envelopes for your successor because you’re changing company willingly or unwillingly.  

 

A lifetime of troubleshooting comes with its ups and downs. Looking back, it has provided many an opportunity to change my career trajectory. For instance, troubleshooting the lack of performance boost from a technology invented by the number one global software vendor almost cost me my job; but it also re-defined me as a professional. I learned to stand up for myself professional. As Agent Carter states, "Compromise where you can. And where you can’t, don’t. Even if everyone is telling you that something wrong is something right, even if the whole world is telling you to move. It is your duty to plant yourself like a tree, look them in the eye and say, no. You move." And I was right.

 

It’s interesting to look back, examine the events and associated time-series data to see how close to the root cause signal I got before being mired in the noise or vice-versa. The root cause of troubleshooting this IT career is one that I’m addicted to, whether it’s the change and the opportunity or all the gains through all the pains.

 

Share your career stories and how troubleshooting mishap or gold brought you shame or fame below in the comment section.

5 Essential Components For Succesful Monitoring Systems

$
0
0

best.jpg

 

On Day Zero of being a DBA I inherited a homegrown monitoring system. It didn't do much, but it did what was needed. Over time we modified it to suit our needs. Eventually we got to the point where we integrated with OpsMgr to automate the collection and deployment of monitoring alerts and code to our database servers. It was awesome.

 

The experience of building and maintaining my own homegrown system combined with working for software vendors has taught me that every successful monitoring platform needs to have five essential components; identify, collect, share, integrate, and govern. Let's break down what each of those mean.

 

Identify

A necessary first step is to identify the data and metrics you want to monitor and alert upon. I would start this process by looking at a metric and putting it into one of two classes: informational or actionable. Metrics that were classified as information were the metrics that I wanted to track, but didn't need to be alerted upon. Actionable are the metrics where I needed to be alerted upon because I was needed to perform some actions in response. For more details on how to identify what metrics you want to collect, check out the Monitoring 101 guide, and look for the Monitoring 201 guide coming soon.

 

Collect

After you identify the metrics you want, you need to decide how you want to collect and store them for later use. This is where flexibility becomes important. Your collection mechanism needs to be able to consume data in varying formats. If you build a system the relies on data being in a perfect state, you will find yourself easily frustrated the first time some imperfect data is loaded. You will also find yourself spending far too much time playing the role of data janitor.

 

Share

Now that your data is being collected, you will want to share it with others, especially when you want to help provide some details about specific issues and incidents. As much as you might love the look of raw data and decimal points, chances are that other people will want to see something prettier. And there's a good chance they will want to be able to export data in a variety of formats, too. More than 80% of the time your end-users will be fine with the ability to export to CSV format.

 

Integrate

With your system humming along, collecting data, you are going to find that other groups will want that data. It could also be the case that you need to feed your data into other monitoring systems. Designing a system that can integrate well with other systems requires a lot of flexibility. It's best that you think about this now, before you build anything, as opposed to trying to make round pegs fit in a square hole later. And it doesn't have to be perfect for every possible case, just focus on the major integration method used the world over that I already mentioned: CSV.

 

Govern

This is the component that is overlooked most often. Once a system is up and running, very few people consider the task of data governance. It's important that you take the time to define what the metrics are and where they came from. Anyone consuming your data will need this information, as well. And if you change a collection, you need to communicate the changes and the possible impacts they may have for anyone downstream.

 

When you put those five components together you have the foundation for a solid monitoring application. I'd even surmise that these five components would serve any application well, regardless of purpose.

Round 1: Barney Fife Vs. Agent K

Test/Development Licenses

$
0
0

Disclaimer: I know that there are other threads on this but I wanted to update it in this new Idea space.


I would really like to have Test/Development licenses for SolarWinds products, at least for the products that we have purchased.  These licenses could be restricted to just a few nodes (like 10ish).

 

The reasons for this would be having the ability to do the following things in a non-production environment...

 

  • Testing upgrades
  • Testing different configurations
  • Learning the SolarWinds products for SCP (SolarWinds Certified Professionals)
    • In the case of SCP's I think they should get access to test licenses for all of the SW products to keep current
  • Creating a small training environment
  • Creating a demo environment

 

I am sure there are other reasons that I have not already thought of, please share if you have them and vote on this idea if you like it!

Optical monitoring for Ciena OME6500 (Nortel)

$
0
0

Hi All,

 

Is there anyone successfull to grab Nortel Optical PM with solarwinds? Because, I've tried that for OSC and ORL parameter didn't success. There are no percentation and graphic for tx/rx. Look the capture below.

But for ETH10G parameter successfully show the percentation and graphic for tx/rx. Look the capture below.

Is there anyone help for this issue? Is there any setting that I missed? I use Solarwinds Orion Platform 2017 and Ciena OME6500. Please share your experience. Thank you.

 

Best Regards


Newbie Question - .NET Framework + Windows Management Framework Package

$
0
0

Hi There,

I'm very new to administrating Solarwinds Patch Manager, so I apologise in advance if I'm asking something stupid.

I noticed SolarWinds Patch Manager has a .NET Framework option under Microsoft in the Client Publishing Wizard (though sadly there are no packages).

This has got me wondering whether it would be possible to create a custom package for Microsoft .NET Framework 4.6.2 and a custom package for Windows Management Framework 4.0 in an effort to mass deploy powershell to our network.

Does anyone have any experience or suggestions on this?

Add Custom time interval selection on the Resources tab

$
0
0

While the Trends tab allows the selection of a Custom time interval, the Resources tab does not. It only supports a set of "Last x" selections.

 

Here's a pair of one-week charts from the Memory tab of Resources for one of my servers:

DrillDown.png

I'd like to be able to focus in on a 24 hour view of December 14, and then maybe an hourly view.

 

For another of my servers, I see this:

DrillDown2.png

Something interesting apparently happened between 3pm and 4pm on December 9 and I'd like to be able to focus in on that period to see what other charts might show something interesting that might be smoothed out too much to see in the week view.

How to change targets of a scheduled Maintenance Task

$
0
0

Hi,

 

In 2015 I created a scheduled Task "Decline Itanium Updates for all WSUS Servers" which run fine. Later I added a fourth WSUS Server to the Task. An older one is now removed. How can I remove it from the Task?

The Server itself is removed from Patchmanager and Domain already.

If I view the Tasks properties it shows me: Selected scope: WSUS Servers - 4 selected servers. In the field below the Servers are listed. All Actions other than "Browse Computers" and "Add subnet" are grayed out so I can not remove the fourth old wsus Server from the Task. This results in an error message if the Task is run - it fails partially:

 

 


Details:
WSUSConnection::Unable to connect to the WSUS Server ([fourth WSUS]) using the account: [Account] The remote name could not be resolved: '[fourth WSUS]'

Need to add a feature to add individual Active directory user to DPA

$
0
0

Hi,

 

Current LDAP authentication of Solarwinds provides the feature of adding only the AD group to the Solarwinds for ADS authentication.

It would be good to provide access to individual user from Active directory as well.

That will help us to provide the access to AD users who are not part of any security group.

Also it will help to provide specific database access to the user in DPA instead of providing access to all the contents of DPA to the user.

 

thanks

Shabeer

Round 1: Luigi Vs. Garth Algar

Round 1: Willow Rosenberg Vs Dr. Emmett Brown

What would you call an IT Emergency?

$
0
0

A user runs up to you and says their is an IT Emergency a user cant print. What would you tell the user?


Tell us about the Alert Central Weekly Report?

$
0
0

Have you clicked on anything on the right-hand panel in the Alert Central weekly stats email? Do you find this content useful?

What's the #1 feature you're interested in with Alert Central?

$
0
0

What feature makes you MOST excited about Alert Central? (If I missed your #1 feature, post it in the comments!)

What do you think of the new Thwack layout?

$
0
0

I didn't even know this was coming! I logged in and Thwack looked waaaaaaaaaaaay different.

 

Thoughts?

What Help Desk Software Do You Use?

Consultant?

$
0
0

Are there any other IT consultants out there?

Viewing all 19354 articles
Browse latest View live


Latest Images