Go to the documentation of this file. 1 #ifndef MessageService_ELadministrator_h
2 #define MessageService_ELadministrator_h
69 class MessageLoggerScribe;
91 std::shared_ptr<ELdestination>
attach(std::shared_ptr<ELdestination> sink);
130 std::list<edm::propagate_const<std::shared_ptr<ELdestination>>>
sinks_;
143 #endif // MessageService_ELadministrator_h
void setIntervals(const ELstring &id, int interval)
void resetSeverityCount()
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventID const &, edm::Timestamp const & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those callbacks
std::vector< int > phases
int severityCounts(int lev) const
void setThresholds(const ELseverityLevel &sev)
ELseverityLevel highSeverity_
const ELseverityLevel & abortThreshold() const
int severityCount(const ELseverityLevel &sev) const
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle brackets
bool any(const std::vector< T > &v, const T &what)
static const std::string source
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Mar
void setLimits(const ELstring &id, int limit)
const ELseverityLevel & exitThreshold() const
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined signature
ELseverityLevel checkSeverity()
bool contains(EventRange const &lh, EventID const &rh)
void setTimespans(const ELstring &id, int seconds)
std::map< ELstring, edm::propagate_const< std::shared_ptr< ELdestination > > > attachedDestinations_
std::list< edm::propagate_const< std::shared_ptr< ELdestination > > > sinks_
T angle(T x1, T y1, T z1, T x2, T y2, T z2)
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventID const &, edm::Timestamp const & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
TEMPL(T2) struct Divides void
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*", "!HLTx*" if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL. It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of "!*" before the partial wildcard feature was incorporated). Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run
void log(edm::ErrorObj &msg)
const ELseverityLevel & highSeverity() const
int severityCounts_[ELseverityLevel::nLevels]
std::shared_ptr< ELdestination > attach(std::shared_ptr< ELdestination > sink)