[
https://issues.apache.org/jira/browse/NIFI-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792864#comment-17792864
]
David Handermann commented on NIFI-12450:
-----------------------------------------
Thanks for the comments [~pvillard].
Although there are no direct replacements, for the reasons stated, this does
not seem like a general capability that should remain supported as part of the
framework.
There are a number of possibilities that could be implemented with in a custom
flow design that could provide alternatives, based on particular use cases.
Custom scripted Processors could make use of the Java
[RuntimeMXBean.getUptime()|https://docs.oracle.com/javase/8/docs/api/java/lang/management/RuntimeMXBean.html#getUptime--]
method to determine a new start, although a shutdown command would be more
difficult to observe.
Another alternative could be any type of custom flow that writes to a file or
sends to an HTTP endpoint indicating running status, functioning as a heartbeat.
These solutions would be specific to various deployment environments, and other
solutions would use other process monitoring and health check systems.
Given the availability of alternatives, do you see any value in maintaining
this function for the next major version?
> Deprecate Bootstrap Notification Services for Removal
> -----------------------------------------------------
>
> Key: NIFI-12450
> URL: https://issues.apache.org/jira/browse/NIFI-12450
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.25.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The NiFi bootstrap process includes optional notification services to send
> email messages or call HTTP resources to indicate when NiFi is stopped or
> started.
> Although this level of notification is useful in some circumstances, it does
> not provide sufficient capabilities to warrant continued maintenance. Various
> service monitoring tools provide more robust health and status checking
> capabilities, and much more flexible notification options. For these reasons,
> the Notification Services should be deprecated on the version 1 support
> branch for subsequent removal in the next major release version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
