You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@streampipes.apache.org by "Dominik Riemer (Jira)" <ji...@apache.org> on 2022/11/26 14:22:00 UTC
[jira] [Commented] (STREAMPIPES-372) Pipeline Health Check
[ https://issues.apache.org/jira/browse/STREAMPIPES-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17639213#comment-17639213 ]
Dominik Riemer commented on STREAMPIPES-372:
--------------------------------------------
This issue has been migrated to https://github.com/apache/streampipes/issues/513
> Pipeline Health Check
> ---------------------
>
> Key: STREAMPIPES-372
> URL: https://issues.apache.org/jira/browse/STREAMPIPES-372
> Project: StreamPipes
> Issue Type: New Feature
> Components: Backend, UI
> Reporter: Dominik Riemer
> Assignee: Dominik Riemer
> Priority: Major
> Fix For: 0.68.0
>
>
> Add a feature that monitors pipeline element endpoints and re-invokes an endpoint in case the endpoint has failed or has been restarted.
> Users should get an information that a pipeline element is not available anymore or has been restored.
> The health check should be triggered by the core until STREAMPIPES-319 is ready, when health checking can be delegated to the service discovery module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)