Thursday Sep 17, 2015

Blank Credentials and Monitoring Delays

I saw a couple of unrelated but short questions this week, so I thought I'd answer them both.

"I tried to edit the credentials used by the Enterprise Controller to access My Oracle Support, but when I open the credentials window, the password field was blank, even though there should be an existing password. What's going on?"

So, naturally, once you've entered a password, we don't want to send that password back to the UI, because it'd be a security risk. In 12.3, though, the asterisks to indicate an existing password aren't showing up. So, your credentials are still there, and they won't be changed unless you specifically enter new credentials and save them.

"I was trying to make sure that file system monitoring was working correctly on a managed system. I made a file to push utilization up past the 90% threshold, which should've generated an incident. However, the incident didn't show up for almost an hour. Why is there a delay?"

You can edit the Alert Monitoring Rule Parameters in Ops Center. However, the thresholds that you set have to be maintained for a certain amount of time before an alert is generated. For a file system utilization alert, the default value for this delay is 45 minutes. You can edit the alert to change this threshold if needed.

Thursday Mar 19, 2015

Tuning Asset Monitoring

The ability to monitor a variety of asset characteristics, like reachability and CPU usage, is one of Ops Center's strengths. However, sometimes you'll want to fine-tune this monitoring capability. Maybe you have a group of important operating systems and you want their monitoring rules to be more stringent, for example.

In cases like that, you can use monitoring policies to fine-tune the way that your assets are monitored. A monitoring policy specifies what thresholds are critical, such as reachability being false (duh) or memory usage being higher than 90%. These thresholds determine when incidents are raised on the monitored assets.

By creating a monitoring policy and applying it to an asset or a group of assets, you can effectively tell Ops Center which information about your assets is important to you, so that you see more signal and less noise.

There's more information about asset monitoring in the Monitoring Rules and Policies chapter of the Feature Reference Guide.

Thursday Sep 26, 2013

Custom Monitoring Policies

In Ops Center, you can create custom monitoring policies to set different monitoring thresholds for different groups of assets. I got a question about how to implement this:

"I'm trying to create a custom monitoring policy that'll be used for all global zones. So I copied the default one, tweaked a threshold and clicked 'Set as Default Policy'. However, even after checking that option, all of my global zones are still using the old monitoring policy. How do I get them to use the new one?"

So, setting a monitoring policy as the default just means that it'll be used for any new assets of that type. So, in this case, new global zones would use your custom policy, but global zones that already have another policy won't automatically switch. To switch your existing global zones over to your new policy, you need to select them (either individually or in a group) and apply the new policy to them. There's an action to do this in the actions pane.

Wednesday Oct 03, 2012

How To: Use Monitoring Rules and Policies

One of Ops Center's most useful features is its asset monitoring capability. When you discover an asset - an operating system, say, or a server - a default monitoring policy is applied to it, based on the asset type. This policy contains rules that specify what properties are monitored and what thresholds are considered significant. Ops Center will send a notification if a monitored asset passes one of the specified thresholds.

But sometimes you want different assets to be monitored in different ways. For example, you might have a group of mission-critical systems, for which you want to be notified immediately if their file system usage rises above a specific threshold. You can do so by creating a new monitoring policy and applying it to the group. You can also apply monitoring policies to individual assets, and edit them to meet the requirements of your environment.

The Tuning Monitoring Rules and Policies How-To walks you through all of these procedures.


This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you


« October 2015