Pipeline Monitoring API start and end Parameters

On https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438155/Pipeline+Monitoring+API for the GET /api/1/rest/public/runtime/?, what do the start and end parameters control and what are some examples of valid values?

Snap: REST Get
Service URL: https://elastic.snaplogic.com/api/1/rest/public/runtime/[your_org_name]
Query parameters: last_hours : [# of hours from now]
Query parameters: limit : [# of records returns]
Has next: ($entity.response_map.offset + $entity.response_map.limit) < $entity.response_map.total
Next URL: ‘https://elastic.snaplogic.com/api/1/rest/public/runtime/[your_org_name]?last_hours=100&limit=1000&offset=’ + ($entity.response_map.offset+$entity.response_map.limit)

If you are ingesting this periodically to a db env, you can obtain max date and do some computation to figure how many hours to set your last_hours dynamically (now - max(date))

According to the doc https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438155/Pipeline+Monitoring+API, isn’t “limit” the number of runtimes, not hours?

I’m just looking on more info on the start and end parameters particularly. My request is related to List started pipelines regardless of start date.

you are correct. I misstated for the limit explanation. I just revised my reply and added the pagination info as well.

1 Like