1. Home
  2. Docs
  3. Monitoring rules
  4. Jeyzer Rules
  5. Attributes


Jeyzer rule attributes

Standard attributes :

  • name : the rule name
  • ref : rule reference id. Must be unique.
    This is a short code to identify the rule instance.
    Compare it to an ORA-XXX code.
    Refs are propagated on the generated events to keep track of their origin.
    Use your own naming convention.
    Recommended one is : Organisation / Rule group / Id.
    Example : ORG-WEB-005
    Jeyzer core rule refs are prefixed with JZR, demo rules with DMO.
  • ticket : issue tracking system id. Optional
    Ticket value can be used by the JIRA publisher to update the associated JIRA ticket.
  • narrative : overrides the default rule narrative. Optional.
    All rules have by default a narrative which describes what the rule does.
  • thresholds: the set of thresholds. See thresholds section

Context attributes

  • param : condition parameter shared between the thresholds
  • param_display : parameter display name, at least used in the generated rule description of its conditions
  • operator : condition comparison operator shared between the thresholds.
    Supported values are : lower_or_equal, greater_or_equal
    Default is greater or equal.
  • extra_info : display rule information required when instantiating a template rule

Hidden attributes

  • source : hidden constant attribute set to Jeyzer Analyzer (unlike the application rule sources)
<rule name="Process card property pattern" param_display="Java runtime version" param="java.runtime.version" ref="JZR-PCD-001" ticket="JIRA-2457">
  <narrative>This rule detects if the Java version is older than Java 8.</narrative>