Skip to main content
Solved

Check engine status using Rest API


Which REST API endpoint to use to check if an engine is offline.

Best answer by Bikram

@saikat_chatterjee 

We don’t have direct rest API call for getting the engine status streamsets DC.

 

You can check under provision section as per given screen shot to findout deployment status with deployment engine details with status.

 

some examples for your reference 

 

https://na01.hub.streamsets.com/provisioning/rest/v1/csp/deployment/2dd74803-c182-4667-b4cb-3ef9b171b6fb:14567cac-c52b-11eb-bee8-6574edbd0001

 

Please try different options with correct restAPI and get the D engine details in it.

 

I also googled to get the engine status and found the URL but i couldn’t get into it to get the details from it.

 https://na01.hub.streamsets.com/rest/v1/system/heartbeat

 

Thanks & Regards

Bikram_

 

View original
Did this topic help you find an answer to your question?

3 replies

Bikram
Headliner
Forum|alt.badge.img+1
  • Headliner
  • 486 replies
  • Answer
  • March 26, 2023

@saikat_chatterjee 

We don’t have direct rest API call for getting the engine status streamsets DC.

 

You can check under provision section as per given screen shot to findout deployment status with deployment engine details with status.

 

some examples for your reference 

 

https://na01.hub.streamsets.com/provisioning/rest/v1/csp/deployment/2dd74803-c182-4667-b4cb-3ef9b171b6fb:14567cac-c52b-11eb-bee8-6574edbd0001

 

Please try different options with correct restAPI and get the D engine details in it.

 

I also googled to get the engine status and found the URL but i couldn’t get into it to get the details from it.

 https://na01.hub.streamsets.com/rest/v1/system/heartbeat

 

Thanks & Regards

Bikram_

 


saleempothiwala
Headliner
Forum|alt.badge.img

@saikat_chatterjee 

 

You should use Subscriptions and event type as Execution Engine Not Responding. It will generate a trigger when the event condition satisfies so you dont have to check at regular interval.

 

Once set up, you can generate a notification on email or webhook whenever the engine(s) are not responsive. There is a configuration that says how many seconds to wait from the last successful heartbeat from the engine. By default it is 300 seconds.

 

You can find more information here: https://docs.streamsets.com/controlhub/latest/onpremhelp/controlhub/UserGuide/Subscriptions/Events.html#concept_gjm_d5t_mfb

 


Thank you @Bikram and @saleempothiwala for your help.


Reply