... | @@ -340,9 +340,14 @@ REST API should be enhanced with the hook endpoint. It should allow a list of ho |
... | @@ -340,9 +340,14 @@ REST API should be enhanced with the hook endpoint. It should allow a list of ho |
|
Supported operations:
|
|
Supported operations:
|
|
|
|
|
|
- `GET /hooks` - list the hooks
|
|
- `GET /hooks` - list the hooks
|
|
- `GET /hooks/{id}` - get the details about a specific hook, including the loading status with occurred errors
|
|
- `GET /hooks/{id}` - get the details about a specific hook, including the loading status with occurred errors, settings, and statistics
|
|
- `PUT /hooks/{id}` - edit hook, i.e., activate/deactivate hook (reload/unload), change the hook parameters
|
|
- `PUT /hooks/{id}` - edit hook, i.e., activate/deactivate hook (reload/unload), change the hook parameters
|
|
|
|
|
|
|
|
Optional operations for diagnostic purposes:
|
|
|
|
|
|
|
|
- `GET /hooks/callouts` - list of the registered callout points
|
|
|
|
- `GET /hooks/callouts/{name}` - detailed info about a specific callout, i.e. list of hooks that registered the callout point, usage statistics
|
|
|
|
|
|
## Hook monitoring
|
|
## Hook monitoring
|
|
|
|
|
|
The hook frameworks should provide a monitoring solution. The hook executor should collect diagnostics information for each hook/callout, e.g., how much time the application spends running a specific callout.
|
|
The hook frameworks should provide a monitoring solution. The hook executor should collect diagnostics information for each hook/callout, e.g., how much time the application spends running a specific callout.
|
... | | ... | |