What file(s) to edit, to configure the Scrutiny app?

Apps and Virtualization
1

I have installed the provided Scrutiny app on all of my TrueNAS Community installations. I want to configure their notifications, but it’s not clear to me what the proper way to do that is, if by GUI, or what file(s) to edit via the shell.

Would someone point me in the right direction, please? Thanks.

This is the only app I have installed on any of my installations, so I’m a bit clueless about them on this platform. I don’t like the idea of my device doing anything other than being a NAS, but this is sort of like an extension to the OS, so seems reasonable to do.

2

The first point is to check the documentation here:

That will tell you where the app expects the configuration. Here it expects scrutiny.yaml or collector.yaml in /opt/scrutiny/config.

Next you can look at the docker volume mounts, with truenas apps you can find them here:

image
image717×103 2.43 KB

In this example the source path /mnt/.ix-apps/app-mounts/scrutiny/config is mounted inside the container as /opt/scrutiny/config.

image
image916×252 11.7 KB

The source path depends on what you selected during install. The above is if you used ixVolumes (which I don’t recommend).

Now that we know where to place the config files on the host in order for them to appear in the container.

I.e. we can place a file in /mnt/.ix-apps/app_mounts/scrutiny/config/scrutiny.yaml and it will appear in the container as /opt/scrutiny/config/scrutiny.yaml.

You can create that file in the shell if you want. Sudoedit is a easy & secure way to create files as root.

Got to shell and execute sudoedit /mnt/.ix-apps/app_mounts/scrutiny/config/scrutiny.yaml. You can copy/adapt the example config file from scrutiny/example.scrutiny.yaml at master · AnalogJ/scrutiny · GitHub. You will have to adapt the file path to your configuration.

Disclaimer: I don’t use scrutiny.

3

Thanks for your reply - I’ll give it a try shortly. I did take the defaults, during installation, so that location IS where my files are. Might I ask why you don’t recommend that location?

4

If the application data is of importance then you want to have control over it. For example you want to setup snapshots policies and backups. Sometimes you want to share it, configure permissions, etc.

If you choose ixVolumes as your data storage you get no control. ixVolumes are created on a hidden dataset. You can’t find them in the UI, you can’t create backups, you can’t create backups etc.

If your app data isn’t important, maybe you’re just testing the app, then ixVolumes are OK to use.

You might also be interested in this quote from the official documentation:

Use ixVolumes to allow TrueNAS to create a dataset on the apps storage pool. Like host paths, ixVolumes are mounted as Docker bind mounts and can be mounted read-only. In most use cases, ixVolume storage is better suited to app testing, while host volumes are better for production deployments.

5

I’ll give that some consideration. Thanks.

6

Just a follow-up to say that your instructions were impeccable. I was easily able to set up notifications for the app. Thanks.

Now I’ll go ponder on where I ultimately want it installed, and how. :slight_smile:

1 Like
7

Just be aware there is a bug in scrutiny in the way it reports command timeout for some drives, you will get a massive number over 4 or 8 billion which in actually means 1 in 65000 odd or 2 in 131000 odd when decoded. See Here