Changes between Version 4 and Version 5 of GENIMonitoring/Alerts


Ignore:
Timestamp:
05/12/15 16:57:13 (5 years ago)
Author:
cody@uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIMonitoring/Alerts

    v4 v5  
    2424Simply, ''CEPE queries'' are pattern-based (matching) subscriptions describing a possible future event. If the described event occurs, a described output is emitted from the CEPE.
    2525
    26 ==== Esper Queries ====
     26==== Esper query format ====
    2727
    2828In a typical database we query existing data based on some declarative language.  We can think of and Esper query like an upside down SQL, where if events occur in the future, results will be emitted.  The Using the ESPER query language, ''EPL'' (similar to SQL) complex events can are described. 
     
    4141
    4242Just as traditional relational databases, and their related SQL queries, use specific data type operations based on column data types, data streams processed by Esper are defined by strongly typed object classes.  In the previous EPL query the ''somefield'' field would have to defined as a numeric time in order for mathematical comparison to work.       
     43
     44==== GENI monitoring stream data format ====
    4345
    4446For GENI Monitoring alerts, we use the LogTick class shown in the code block below:
     
    7274}}}
    7375
     76==== Example GENI monitoring stream queries ====
     77
     78
     79* Ping times greater than 10,000ms
     80{{{
     81select * from LogTick(metric='ping_rtt_ms') where value > 10000.0
     82}}}
     83
    7484
    7585*Image from RabbitMQ tutorial [https://www.rabbitmq.com/tutorials/tutorial-three-python.html]
    76 *Image from Esper [http://www.espertech.com/]
     86
     87**Image from Esper [http://www.espertech.com/]