search cancel

ASM monitor API LocationID not getting set

book

Article ID: 240819

calendar_today

Updated On:

Products

CA App Synthetic Monitor

Issue/Introduction

I was able to get the list of locations using the API call, but when I add the locationId (check points/public station/OPMS) value to the create monitor API call it does not set a specific location (check point). It still creates the monitor with all locations selected.

Environment

Release : SAAS

Component : APP SYNTHETIC MONITOR ENVIRONMENTAL

Resolution

Instead of using the following in your payload.

 \"locationId\": 326}

Please use the following 

\"checkpoint\":{\"usePublic\":false,\"groupIds\":[46,206,10680],\"algorithm\":\"sticky\",\"defaultGroupId\":null}

These are three check points for the monitor:

[46,206,10680]

You must use minimum 3.

Go to the UI and check the locations. Once you see that check point locations are selected properly, then you can make adjustments in check point values.  

The above three checkpoints are as following:

San Antonio, Texas - 1 station(s)

San Francisco - 1 station(s)

Seattle, Washington - 1 station(s)

If it is on promise monitoring station then one ID is ok.

example:

"groupIds": [
      820
    ],

820 is a on promise monitoring station in the account where monitor is being added.

Full example of the API call is attached. I can be tested with v3 API. https://api.asm.saas.broadcom.com/v3