Guillaume Lhermenier created NIFIREG-443:
--------------------------------------------
Summary: Provide a status API endpoint
Key: NIFIREG-443
URL: https://issues.apache.org/jira/browse/NIFIREG-443
Project: NiFi Registry
Issue Type: New Feature
Affects Versions: 0.8.0
Reporter: Guillaume Lhermenier
As Nifi registry exposes an API, it should be really helpful to also expose a
status/healthcheck endpoint.
When deploying a nifi-registry in any cloud provider, I think almost nobody
wants to parse something like
{code:bash}
[root@nifireg bin]# ./nifi-registry.sh status
nifi-registry.sh: JAVA_HOME not set; results may vary
Java home:
NiFi Registry home: /opt/nifi-registry-0.8.0
Bootstrap Config File: /opt/nifi-registry-0.8.0/conf/bootstrap.conf
2021-03-08 13:30:51,178 INFO [main] o.apache.nifi.registry.bootstrap.Command
Apache NiFi Registry is currently running, listening to Bootstrap on port
35989, PID=635
{code}
A simple
{code:java}
/status{code}
endpoint returning whether the nifi registry is running fine or not should be
sufficient.
Also, if it could be UNsecured (not sure we should have to handle certs to just
know if the service is running or not.), it could be veeeeeery well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
