From Service Health Database Query API to ss_t

Hi

 

I use Service Health Database Query API  to extract a XML dashboard like

 

- <node name="PORT: *********" id="1;;ed3b6d42bf8d0557f1dc35cd287777d3;;db6340a8770cf57bcb69658d7245e850;;632cbe037dd1ac43fb814405d2005e58;;a18d0e22ce14b65ace2f4c48bac2b523" cmdbId="a18d0e22ce19b20ace2f4c48bac2b523" ciType="sitescope_monitor" layer="null" classification="null">
<dimension name="Legacy System" status="-3" id="1">null</dimension>
<dimension name="Application Availability" status="-3" id="7">null</dimension>

 

I would love to find a key in the above that I can use to query a BSM sitescope tabel either ss_t or ss_hr_t.

Could there be a connection between Service Health Database Query API and ss_t (or ss_hr_t)?

 

thanks

Henrik

 

Tags:

  • Access to metric samples (ss_t, trans_t etc.) is provided via a totally different API - Generic Reporting Engine API. If you are interested in using this API, you can find more details in a corresponding chapter of the BSM Extensibility guide.

  • Thanks Dmitry

    I  already use Generic Reporting Engine API to extract BPM information from trans_t.

    But my problem is that I can't use any of the information I get from the Service Health Database Query API as key to a query in Generic Reporting Engine API.

     

    From Generic Reporting Engine API I get:

    <node name="PORT: *********" id="1;;ed3b6d42bf8d0557f1dc35cd287777d3;;db6340a8770cf57bcb69658d7245e850;;632cbe037dd1ac43fb814405d2005e58;;a18d0e22ce14b65ace2f4c48bac2b523" cmdbId="a18d0e22ce19b20ace2f4c48bac2b523" ciType="sitescope_monitor" layer="null" classification="null">
    <dimension name="Legacy System" status="-3" id="1">null</dimension>
    <dimension name="Application Availability" status="-3" id="7">null</dimension> 

     

    Very fine, but there is not a unique key that I can use to query ss_t.

     

    To query ss_t I need a unique key like "ci id" or "monitor id" and none of them are included in the Service Health Database Query API output.

     

    It does not seem like any of the below can be used:

    **********id="1;;ed3b6d42bf8d0557f1dc35cd287777d3;;db6340a8770cf57bcb69658d7245e850;;632cbe037dd1ac43fb814405d2005e58;;a18d0e22ce14b65ace2f4c48bac2b523" cmdbId="a18d0e22ce19b20ace2f4c48bac2b523"******