getMemoryUsage in Tibco Hawk rulebase

Tags

business works, ems, hawk, monitor memory, solaris, tibco, unresolved, unresolved for weeks

Operating Systems Solaris getMemoryUsage in Tibco Hawk rulebase

02-18-2009

Registered User

8, 0

Join Date: Feb 2008

Last Activity: 15 May 2009, 5:55 AM EDT

Posts: 8

Thanks Given: 0

Thanked 0 Times in 0 Posts

getMemoryUsage in Tibco Hawk rulebase

We have a Hawk rulebase monitoring memory usage on a Tibco BW process. We have it set to alert if memory usage goes above 96%.

It is now telling us that usage has reached 96% but we don't know why this is as there is no discernible increase in the number of ems messages that the process is dealing with.

Any ideas about why this would happen or how we can control it. Do we need to take some remedial action with this process to reduce this usage from 96%??

Any help appreciated...

billy_mega

View Public Profile for billy_mega

Find all posts by billy_mega

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Red Hat

Rsyslog implementation using rulebase

Hi All, Can anyone guide me how to setup rsyslog using rule base, Templates , Modules and mmnormalize.. I have gone through rsyslog site ..But not able to get idea how to set the rsyslog.conf using rulebase particularly.. Thanks in advance ..

2. HP-UX

how to log into a tibco server?

how to log into a tibco server from unix ?

LEARN ABOUT HPUX

kcmond

kcmond(1M)																kcmond(1M)

NAME

       kcmond - EMS Kernel Tunable Monitor daemon

SYNOPSIS


		kcmond

DESCRIPTION

       The  kcmond  daemon  monitors  the consumption of kernel resources. It is an Event Monitoring Services (EMS - see ems(5)) monitor. The data
       collected by kcusage can be displayed by kcusage(1M).

       kcmond includes a resource dictionary file (/etc/opt/resmon/dictionary/kcmond_01.dict) which is used by EMS to identify resources for moni-
       toring.

       Users can control the monitoring of each kernel tunable by setting a percentage value for the consumption of that resource. For example, if
       the user sets a value of 75 for nproc, the Kernel Tunable Monitor will report an event when the number of  processes  reaches  75%  of  the
       nproc setting.

       The  kcalarm(1M) command is used to add, modify and delete kernel tunable alarms. The kcusage(1M) command is used to view data collected by
       kcmond. The kcweb(1M) command provides a Web-based, graphical user interface to control alarms and view usage data, including graphs of the
       usage data.

       kcmond is a light weight daemon that will exit after being idle for ten minutes.

SUPPORTED PARAMETERS

       For a complete list of the kernel tunables that can be monitored with this daemon, see the kcusage(1M) manpage.

DEPENDENCIES

       kcmond must be run by the registrar process of the Event Monitoring Service (EMS) and is not designed to be run from the command line.

AUTHORS

       was developed by Hewlett-Packard.

FILES

       Executable.

       The  resource dictionary for kcmond, describes the location (e.g. /system/kernel_tunables/nproc) of kernel tunables in the resource hierar-
       chy and references kcmond as the resource monitor.

       Log file for the entire Resource Monitor Framework, including kcmond. Any errors are logged here.

SEE ALSO

       kcalarm(1M), ems(5), kcusage(1M)

																	kcmond(1M)

Solaris