Configuration Inspector App¶
Configuration Inspector App is a standalone application, separate from Kylo UI and Services and its purpose is to check whether Kylo UI and Kylo Services are configured correctly or not. It comes with a number of Configuration Inspections out-of-the-box and is designed to be easily extensible.
Here is a screenshot of how it may look like:
Inspector App is distributed with Kylo. It is installed as a service and can be found in
You can start/stop/restart Inspector App service in the following way:
service kylo-install-inspector start service kylo-install-inspector stop service kylo-install-inspector restart
Once the service is running, open your browser and find Inspector App at
Find the logs in
Click the circular “Download Report” button closer to the right top corner just above the Inspections list to download and share the inspection report produced by Inspector App.
Add Custom Configuration Inspections¶
AbstractInspectionclass found in
kylo-install-inspector-apimodule. At minimum you will need to implement three methods where the one which does the work looks like this:
public InspectionStatus inspect(Configuration configuration). Via
Configurationclass you get access to Kylo UI and Services properties, e.g.
Configuration.getServicesProperty(String propertyName). You can either directly @Inject Kylo classes into your Inspections or you first create Spring configuration which defines the beans, e.g. see NifiConnectionInspection and NifiConnectionInspectionConfiguration which uses custom Spring configuration to get
JerseyClientwhich can talk to Nifi.
- Package your custom Inspections into a
- Add your jar and its dependencies to Inspector App classpath, i.e. drop them into
- Run Inspector App as usual