Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-) Softpanorama Search

Tivoli Enterprise Console Tips

Tivoli-IBM TME10 - Tivoli Enterprise Console Tasks 3.9

Hallo,

you have to setup a timer rule that checks after a given time if the event is still open. If that is the case, you send email to another person. Tricky part is to choose where to set the timer. If you set the timer on the event itself, you might end up with a CPU hog if this occurs often. The timer limit is still 1000 (upto 3.6 it was 100!).
Better way is to use the "eternal" TEC_Tick event which is always available. You'd have to set a timer initially in a TEC_Start rule:


rule: tecstart: (
  event: _tick of_class 'TEC_Tick',
  action: ( set_timer(_tick,60,'TEC heartbeat') )
).

Then, on timer expiry you reset the timer to its previous value and do whatever you want to have done. In your case you get the current time, calculate the difference to date_reception of your 'whatever' class event, and if the difference exceeds your limit the admin gets fired ;) because the 2nd email goes to HR.

timer_rule: tectick: (
  event: _tick of_class 'TEC_Tick',
  timer_info: equals 'TEC heartbeat',
  action: (
/* first set the timer again */
    set_timer(_tick,60,'TEC heartbeat'),
/* look for other events */
    first_instance(event: _what of_class 'whatever'
       where [ status: equals 'OPEN',
               date_reception: _when ]),
/* do something with the _what event */
      get_time(_cur_time),
      _age is _cur_time - _when,
      _age > 300,
      exec_task(...),
).

There might be some typos here, read the rules reference at $BINDIR/../generic_unix/TME/TEC/BOOKS/HTML/reference.html.

Tschau...Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"

Senior Consultant, Tivoli Certified Enterprise Consultant + Instructor
santix AG, +49-89-321506-0, Fax -99      www.santix.de, info@santix.de
Weihenstephaner Str. 4, D-85716 Unterschleissheim, GSM +49-171-4416678

STE: IBM Tivoli Enterprise Console 3.9 Global Variables and Fact Files: A Custom Solution to a Custom Problem

Notification and Escalation Rules Customization for TEC 3.9.

IBM Tivoli Enterprise Console 3.9  Understanding the Event Threshold Ruleset

Custom Action To Reset Event Status Before Sending To The TEC Server

Truncating Long Slot Values So TEC Can Process These Events

TEC logfile adapter support for syslog-ng on SLES 10 linux

Sending events to the TEC Server via Non-TME if TME Method Fails

Determining tec_gateway and state based correlation performance

Orb Data tips -  Enterprise Console

• Filtering Events on non-root attributes
  This tip reviews the technique for defining an Event Group that filters on a non-standard, or extended, Event Class attribute (slot)
• Automatically Creating Event Group Filters
  This tip presents a script – smartfilter.pl – that accelerates the process of creating TEC Event Group filters.
• TEC Rules if-then-else Conditions
  How can you construct if-then-else conditions in TEC PROLOG rules? This tip describes the construct.
• Perl DBI Quick Reference
  Provides an overview of accessing data from a database using Perl DBI. Also provides a quick reference to the main functions of Perl DBI, giving examples of how to retrieve data and update it in a database
• Creating TEC Consoles in non-TEC TMRs
  Creating TEC Consoles in non-TEC TMRs
• TEC Rules Based on Time
  This tip supplies and explains a solution to allow TEC to respond to an event based on the time of day
• TEC and Query Libraries
  Provides an explanation of how Queries and QueryLibraries can be used with the TEC database to aid the TME support process. Along with the explanation it also includes a number of sample queries and the CLI to create them
• Event Sensitive Help from the TEC Console
  Describes how you can how you can add event sensitive help to the Event Console, by launching a Web Browser containing help information for that event
• Adding a new message to a Logfile Adapters
  Provides an expanation of how to add new messages to be processed by the Unix Logfile adapter or the NT Event Log Adapter.
• Altering the Width and Name of TEC Console Fields
  Describes how you can change the width and names of the various columns within an EventConsole.
• Multiple Inheritance in BAROC
  This tip presents the advantages of using multiple inheritance in your class definitions and also provides a utility to aid in the creation and use of complex class definitions.
• Implementing TEC only TMRs
  This tip describes a procedure for implementing a combination of non-TEC TMRs and TEC TMRs in your environment to help improve performance of both the TEC server and the TMR server, and to reduce the affect of heavy processing on one another.
• System Heartbeats with TEC - Monitoring by Exception
  Provides the second part of a two part explanation of the use of system heartbeats to display the status of your key systems. This method monitors by exception, displaying only those systems that have missed a specified number of heartbeats for a specified time. Included in this tip are all of the rules, classes and external scripts required.
• TEC: Message Time Limits
  Provides an explanation of the use of TEC Message Diaplay Limits and how they can be viewed and configured through the CLI.
• BAROC Class Navigator
  This tip presents a web based application - the BAROC Class Navigator that allows you to view your BAROC definitions through a web interface. The application displays all of your rule bases, and the class definitions for those rulebases including enumerations, slots slot types and any defined facets.
• TEC Rule Tracing (Part 1)
  This is the first part of a three part tip which takes a closer look at Rule Tracing. This tip describes how you can generate your own trace messages to help debug your rules
• Listing Available TEC Templates/Predicates
  Describes how you can view all of the templates that are in use within your Event Server.
• TEC Rule Tracing (Part 2)
  This is the second part of a three part tip which takes a closer look at Rule Tracing. This tip describes how you can dynamically turn on and off tracing within your rulebase without having to perform a restart.
• Event Cache Demystified
  Aims to demystify the event cache by explaining what it is, what it's used for and how it can or should be configured.
• Troubleshooting BAROC Problems
  Using a recent problem this tip illustrates an example of how you can troubleshoot BAROC Class problems, and describes what is happening during the loading of a rule base and the starting of the Event Server.
• TEC Rule Writing - how to use Assertion Lists
  This tip looks at using assertion lists to preven events from being displayed in the Event Console until a certain threshold has been met
• TEC Rule Tracing (Part 3)
  This is the final part of a three part tip which takes a closer look at Rule Tracing. This tip describes how you can trace particular rules or actions within a rule base, thus allowing you to trace only the rules that you're currently developing.
• Changing TEC Console Display Properties
  Provides a method and script for changing the display properties of a TEC Console from the CLI. This will allow you to preconfigure consoles for Administrators during implementation phase of your projects.
• Common Event Cache Problems
  Describes some common problems associated with the Event Cache, and also some utility rules for dumping and counting the events in the EventCache.
• Event Group Filters
  Explains how other filters can be used in addition to the documented asterix (*) to provide further string filtering when defining your Event Group Filters.
• System Heartbeats with TEC - a state engine approach
  Provides the first part of a two part explanation of the use of system heartbeats to display the status of your key systems. This method uses a state engine, in order to describes the current status of the systems - whether they're available, unavailable, initialising or stopping. Included in this tip are all of the rules, classes and external scripts required.
• TEC Database Internals
  Provides an explanation of the internal workings of the TEC database, including the actions that occur at a database level during Event Server startup, when an event is recieved and when an event is acknowledged or closed.