||Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix|
|News||Tivoli||Recommended Links||Selected Docs||TEC Perl scripts||State correlation engine|
|System Heartbeats with TEC||TEC troubleshooting||Sending events to TEC from scripts||Gateway||Event Adapters||RIM layer|
|TEC event console event viewer||Rules Programming||Testing TEC rules||BAROC||Operations with the rulebase||Fixpacks|
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',
/* first set the timer again */
/* look for other events */
first_instance(event: _what of_class 'whatever'
where [ status: equals 'OPEN',
date_reception: _when ]),
/* do something with the _what event */
_age is _cur_time - _when,
_age > 300,
There might be some typos here, read the rules reference at $BINDIR/../generic_unix/TME/TEC/BOOKS/HTML/reference.html.
"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
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.
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.
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.
The TEC Event Server will not process events through the rules engine if they come in as closed.
The TEC Server will not process events in which the msg slot is very large
The default syslog on SLES 10 is syslog-ng, not the old BSD-based syslogd
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.
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
Even if hostname and origin IP value are defined in the (w)postemsg invocation, this still asks DNS to find the origin IP value
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
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
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
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
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
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: March 12, 2019