forked from Netflix/eureka
-
Notifications
You must be signed in to change notification settings - Fork 0
Eureka REST operations
karthik-vn edited this page Sep 4, 2012
·
18 revisions
Operation | HTTP action | Description |
Register new application instance | POST /eureka/v2/apps/ | Input: JSON/XML payload HTTP Code: 200 on success |
De-register application instance | DELETE /eureka/v2/apps// | HTTP Code: 200 on success |
Send application instance heartbeat | PUT /eureka/v2/apps// | HTTP Code: * 200 on success * 404 if doesn’t exist |
Query for all instances | GET /eureka/v2/apps | HTTP Code: 200 on success Output: JSON/XML |
Query for all instances | GET /eureka/v2/apps/ | HTTP Code: 200 on success Output: JSON/XML |
Query for a specific / | GET /eureka/v2/apps// | HTTP Code: 200 on success Output: JSON/XML |
Query for a specific | GET /eureka/v2/instances/ | HTTP Code: 200 on success Output: JSON/XML |
Take instance “out of service” | PUT /eureka/v2/apps///status?value=OUT_OF_SERVICE | HTTP Code: * 200 on success * 500 on failure |
Put instance back into service | PUT /eureka/v2/apps///status?value=UP | HTTP Code: * 200 on success * 500 on failure |
- Eureka at a glance
- Configuring Eureka
- Building Eureka Client and Server
- Running the Demo Application
- Configuring Eureka in AWS Cloud
- Understanding Eureka Client/Server Communication
- Eureka REST operations
- Understanding Eureka Peer to Peer communication
- Overriding Default Configurations
- FAQ
- Javadoc-Eureka Client
- Javadoc-Eureka Server
- End-to-End Examples