Hi Mark, Bulletins are typically generated when using the component logger from getLogger() and logging something at the WARN or ERROR level, so you should be able to do this wherever is needed in your controller service.
As far as automatically disabling the controller service, I'm not sure there is any way for the component to essentially shut itself down. You might be able to make a call to the REST API [1] to disable the component. -Bryan [1] https://nifi.apache.org/docs/nifi-docs/rest-api/index.html On Thu, Sep 29, 2016 at 1:49 PM, Mark Bean <[email protected]> wrote: > In a Controller Service, bulletins are issued when an exception is thrown > in the @OnEnabled method. However, I would like to issue a bulletin from > other methods in the CS. in this use case, the CS connects to a socket for > a remote lookup service. If the remote service becomes unavailable, it > would be nice to be notified such as with a bulletin. Alternatively, could > such a condition cause the CS to become disabled? In other words, can the > @OnDisabled method be called explicitly and not through the framework? Are > there other suggestions on how to handle this case? >
