DX Infrastructure Manager

  • 1.  Modifying disk usage alarm in cdm

    Posted 01-21-2019 09:50 AM

    Could someone suggest me a possible solution here please

     

    ENVIRONMENT
    ====
    UIM 9.0.2
    cdm 6.33

     

    Issue
    ====
    Using the cdm probe to monitor the disk usage, the current alarm for data breach is like below for example:

     

    Average (1 samples) disk free on C:\ is now 7%, which is below the error threshold (10%) out of total size 99.9 GB

     

    Customer's requirement is to get alarm in the below format:

     

    Average (1 samples) disk used on C:\ is now 93%, which is below the error threshold (10%) out of total size 99.9 GB


    WHAT WE HAVE DONE SO FAR
    ====
    Upon observation, have found from cdm probe GUI-> setup -> Message definitions -> DiskError contains the below Message text:

     

    Average ($value_number samples) disk free on $drive is now $value$unit, which is below the error threshold ($value_limit$unit) out of total size $size_gb GB

     

    Modified the above text to:

     

    Average ($value_number samples) disk used on $drive is now (100-$value$unit), which is below the error threshold ($value_limit$unit) out of total size $size_gb GB

     

    But the result alarm shown is:

     

    Average (1 samples) disk used on C:\ is now (100-7%), which is below the error threshold (10%) out of total size 99.9 GB

     

    TO ASK
    ====
    Is it possible to edit the Message definition in the cdm probe to meet the requirement?
    Or LUA script needs to be written, could someone help me out with the LUA script please



  • 2.  Re: Modifying disk usage alarm in cdm

    Posted 01-21-2019 03:39 PM

    It would be fabulous to have some sort of simple formatting language that could be applied to messages. As well as simple math and simple string manipulation. 

     

    But unfortunately you only get the variables that the developer/product designer thought that you'd like to use.

     

    It should be possible to manipulate this in a preprocessor script - locating the percentage, extracting the value, then doing the math is pretty easy in LUA. (as opposed to using an AO profile - though it depends on the usage.)