Rulebases
How many rules can you have in a rulebase? How many rulebases can you load onto an agent? How many alerts can you generate?
There is no theoretical limit to the number of rules you can have in a rulebase or the number of rulebases a TIBCO Hawk agent can process. However, you may experience a practical limit in terms of memory use, speed, and operating system limitations such as the maximum number of open files per process.
Platform: Not Specified
Version: All
If I use one rulebase across many computers, can I disable some rules on some computers?
You might think that turning on and off rules would be a good way to adapt a rulebase for use on many slightly different computers. However, it presents a problem. If you could disable rules on individual agents, any rulebases distributed across the network would remove those differences, because the rulebases would still have the same names.
One of the most important parts of planning your monitoring effort is deciding how rules must be organized into rulebases and how rulebases are to be distributed over your network. Rulebases can range from very general (for example, all_computers) to very specific (for example, important_app). You might have a set of rulebases you can mix and match to meet the specific needs on each computer.
So if you need to tailor rulebases to specific computers, we suggest that you first look at what functions those computers are performing and how those functions can be organized into rulebase distributions. If you find that you have completely individual needs for each computer, the best approach is to design a rulebase with a unique name that corresponds to that computer.
Platform: Not Specified
Version: All
What rulebases are available with the TIBCO Hawk monitoring software?
The TIBCO Hawk software provides OS-specific rulebases for the platforms supported by it, as well as agent and RV rulebases. You can find all these rulebases stored under HAWK_HOME/examples/rulebases where HAWK_HOME is the directory where the TIBCO Hawk software is installed.
Platform: Not Specified
Version: All
Why does the Posted Condition display as PostedConditionExist
?
In the Rulebase Test Editor, if PostedCondition
is specified as ${Posted.x} > 0
and saved, it is displayed by the Test editor as PostedConditionExist
when you reopen the rulebase. Both of these represent the same expression. Similarly, ${Posted.x} == 0
is displayed as !PostedConditionExist
.
When I use the external variable such as ${External.testvar}in rulebase action type execute or method:Custom:Execute
on Microsoft Windows platform, while variable file is specified as for example: testvar=c:\temp\abc.bat, it does not work. What's wrong?
In the Microsoft Windows environment, when you specify the variable file which contains a directory path, instead of specifying
testvar=c:\temp\abc.bat
you should use forward slash or another backward slash to escape the '\', such as:
testvar=c:/temp/abc.bat
or
testvar=c:\\temp\\abc.bat
And this would solve the problem.
Platform: Windows