This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SnapLogic REST Endpoint to get pipeline runtime details using ruuid

wani-amol
New Contributor III

‎05-23-2019 09:59 AM

Hello all,

I am using SnapLogic’s REST Endpoint https://elastic.snaplogic.com/api/1/rest/public/runtime
to access one of our pipeline’s runtime details using the pipeline’s ruuid.
Our objective is to get the pipeline logs, write those in our sql db process log table and email the log in case we hit an error and the pipeline fails.
It has been running successfully so far. Is there a way to know if the endpoint is changed or if there are any other changes due to which the existing pipeline could break?
Also, is this a good practice or is there a better way to achieve this?

0 Kudos
6 REPLIES 6

vkbeemanapalli
Employee
Employee

‎05-24-2019 02:43 AM

When you say it has been running successfully so far > has it returned an error or do you see any changes in the data captured at the endpoint. You can try validating the account and see if any changes caused this behavior.

There is another way to get the logs from the snaplex using LogAPI

https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438932/Log+API

If you are trying to read only failed runtimes it would be simpler and use the runtime API based on state of the pipeline. You are using this anyway.

0 Kudos

wani-amol
New Contributor III
In response to vkbeemanapalli

‎05-24-2019 06:18 AM

Thanks for the quick reply! I should have worded my question better, I wanted to know if the endpoint changes in future, is there a way to be notified about it or it won’t?
I’ll use the log API from now.

0 Kudos

tlikarish
Employee
Employee
In response to wani-amol

‎05-24-2019 07:14 AM

We’ve tried to keep all public api’s stable and if there is a change that breaks a consumer of the API, then I’d consider that a bug that should be fixed. If there was a backwards incompatible change, then we’d probably add a new endpoint or bump the version number, /api/2/rest/public/runtime, for the endpoint.

If you have any ideas how we could build better auditing/governance into our platform, feel free to share them in the enhancement requests section for discussion.

0 Kudos

wani-amol
New Contributor III
In response to tlikarish

‎05-24-2019 08:03 AM

Awesome. The API works fine for our use-case and it is great to know there is support in case anything breaks. Thank you for the information. I really appreciate your quick response. 🙂