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, [email protected]
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

Abstract: One of the most common challenges in a large event management system is to determine where a received event should go.

In small TEC environments this is not a big problem, the event filtering capability of the TEC console is sufficient to ensure the event gets to the proper administrators.

In larger environments, the event filtering capability may not be the appropriate tool.

Often the event filter specifications become unmanageable and should there be a need to reinstall or move the TEC.

Notification and Escalation Rules Customization for TEC 3.9.

Common customizations of the Notification and Escalation rulesets shipped with Tivoli Enterprise Console 3.9 (TEC 3.9) can be done quickly and efficiently. These can improve event management productivity. Examples will be shown to illustrate customizations in a supported fashion. Ralph Baldwin will present on these topics on January 9, 2007.

IBM Tivoli Enterprise Console 3.9  Understanding the Event Threshold Ruleset

This STE is intended to provide an understanding of the supplied event_thresholds.rls ruleset. Areas covered will cover areas such as

• looking in detail at the ruleset,
• how it works and how to trace and interpret the output.

It will be presented by David Leftwich on January 18, 2007.

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

The TEC Event Server will not process events through the rules engine if they come in as closed.

Truncating Long Slot Values So TEC Can Process These Events

The TEC Server will not process events in which the msg slot is very large

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

The default syslog on SLES 10 is syslog-ng, not the old BSD-based syslogd

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

If TME Communications fail to send an EVENT to the TEC Server, how can that event be sent via NON-TME Communications instead of caching the event.

Determining tec_gateway and state based correlation performance

In large and small environments, it may be necessary to look at how much time it takes for the tec_gateway process to receive an event, pass it to state based correlation, get it back from state based correlation and send it on to the TEC Server

Origin before hostname in (w)postemsg usage to avoid DNS requests
 

Even if hostname and origin IP value are defined in the (w)postemsg invocation, this still asks DNS to find the origin IP value

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.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019