DX Infrastructure Manager

Expand all | Collapse all

Develop Monitor for QoS with probe-sdk 2.5.0

Jump to Best Answer
  • 1.  Develop Monitor for QoS with probe-sdk 2.5.0

    Posted 01-05-2018 09:27 PM

    I am using the Java probe-sdk 2.5.0 to develop a probe that generates QoS dynamically, but I need to modify the profile to add a monitor each time a new QoS is generated.
    For example, for the QoS "Disk State" I need to configure the monitor to publish the value and alarm, indicating that when the value is 0 send an error alarm:

     

    <monitors>
    <0>
    active = true
    device = SymDisk
    qos_on = true
    name = 000292604376.Disks.DF-10A.C.1.Disk State
    alarm_on = true
    rule = current
    key = "ESC:SymDisk:Prueba::000292604376::Disks::DF-10A.C.1"."DiskState"
    <alarms>
    <0>
    msg = StatusError
    thr = 0
    oper = =
    </0>
    </alarms>
    </0>
    </monitors>



  • 2.  Re: Develop Monitor for QoS with probe-sdk 2.5.0

    Posted 01-05-2018 09:53 PM
      |   view attached

    I'm not sure if this is exactly what you are looking for but there was a custom probe written some time ago to generate QoS. There are no release notes in English. I've attached the qos_generator v1.50 probe package.

     

    -   The probe requires java jre v1.6.

     

    You can use this qos_generator probe in your TEST machines to generate qos messages. Its not meant for production environments.

     

    QOS Generator Usage

     

    What is the QOS Generator?
    -    The QOS Generator is a custom probe that uses CSV files to generate QOS metrics.

     

    How does it work?
    -    It uses CSV files with 24 columns to generate the different parts necessary for a proper QOS metric. This includes the QOS Definition, the S_QOS_DATA information, the RN table information and also the required CM_* tables in the database.

     

    How do I edit the CSV file to include the QOS metrics I want to generate?
    -    First, the qos_generator probe will ignore the first line, so feel free to keep the headers intact for ease of use. Now, onto the columns:
    1)    QOS – This is the QOS metrics name from the S_QOS_DATA table
    2)    SOURCE – The metric source
    3)    TARGET – The metric target
    4)    SAMPLETYPE – This will be 0 (ZERO)
    5)    VALUE_FLOOR – The minimum value you want randomly generated
    6)    VALUE_CEILING – The maximum value you want randomly generated
    7)    SAMPLESTDEV – Leave this at 0 (ZERO)
    8)    SAMPLERATE – The probe only generates at the probe interval, so leave this at 300
    9)    SAMPLEMAX – If the metric has a maximum value enter it here, default is 0 (ZERO)
    10)    DEF_NAME – S_QOS_DEFINITION qos name, will be the same as column 1
    11)    DEF_QOS_GROUP – S_QOS_DEFINTION qos group name
    12)    DEF_DESC – S_QOS_DEFINITION qos description
    13)    DEF_UNIT – S_QOS_DEFINITION qos unit
    14)    DEF_ABBR – S_QOS_DEFINTION qos unit abbreviation
    15)    DEF_HASMAX – If the qos metric has a maximum value, enter -1 here and if there is no maximum value enter 0 (ZERO)
    16)    DOMAIN – The Nimsoft domain name
    17)    ROBOTIP – IP Address of the robot (real or fake) the data is to be collected from
    18)    SOURCE – Source of the metric
    19)    ROBOT – Robot name (real or fake) the data is to be collected from
    20)    ORIGIN – Origin of the metric
    21)    PROBE – Probe collecting the metric (Can be anything)
    22)    SEED – Number to help randomize the graphing (between 1 and 1000000)
    23)    CI_TYPE – This information can be found by querying the CM_CONFIGURATION_ITEM_DEFINTION table in the database
    24)    METRIC TYPE – This information can be found by querying the  CM_CONFIGURATION_ITEM_METRIC_DEFINITION table in the database

     

    Probe Notes:

     

    -    Must be deployed to a hub
    -    In its current version, the qos_generator requires a HOST file entry for any robot in the CSV. You can run Notepad as administrator and open it from the following location (C:\Windows\system32\drivers\etc\hosts).
    -    If you are making a custom metric, please use CI and METRIC id in the 9.x range.

    Attachment(s)

    zip
    qos_generator_1.50.zip   151K 1 version


  • 3.  Re: Develop Monitor for QoS with probe-sdk 2.5.0

    Posted 01-08-2018 06:50 PM

    Hi Stephen,
    Thank you for your answer.
    But I need to create a monitor in probe execution time.



  • 4.  Re: Develop Monitor for QoS with probe-sdk 2.5.0

    Posted 01-15-2018 09:20 AM

    Hello Carlos,

     

    you may have to get in contact with CA Services to get further assistance with this question.

     

    Kind regards,

    Britta Hoffner

    CA Support



  • 5.  Re: Develop Monitor for QoS with probe-sdk 2.5.0
    Best Answer

    Posted 01-15-2018 10:13 PM

    If you want to have a conversation with me directly, I will try to show you some examples of creating QOS and alarms with the SDK.

     

    bryan.morrow@ca.com

     

    Bryan