Scrutiny notifications setup
reddit / selfhosted

----------------------------------------------------------------------
thimplicity · 2023-10-22 19:25

Hi everyone,

I am using the Scrutiny smart monitoring and it works fine. I am using
it in a hub and spokes principle, meaning that I run the web portion
in via docker and the "spokes" have a daily cronjob and send the
results to the hub. The only thing I cannot get to work are the
notifications. I use pushover. I have documented the issue on
[github](https://github.com/AnalogJ/scrutiny/issues/498), but
unfortunately no response. I thought maybe someone here had the same
challenge. I don't think it is a pushover problem, but rather how I
used docker compose:

    version: '2.4'

    services:
      influxdb:
        image: influxdb:2.2
        container_name: scrutiny-influxdb
        ports:
          - '8186:8086'
        volumes:
          - '/docker/scrutiny/influxdb:/var/lib/influxdb2'
          - influxdb:/etc/influxdb2
        environment:
          - INFLUXDB_ADMIN_USER=...
          - INFLUXDB_ADMIN_PASSWORD=...
        healthcheck:
          test: ["CMD", "curl", "-f", "http://localhost:8086/health"]
          interval: 5s
          timeout: 10s
          retries: 20

      web:
        image: 'ghcr.io/analogj/scrutiny:master-web'
        container_name: scrutiny-web
        ports:
          - '8180:8080'
        volumes:
          - '/docker/scrutiny/config:/opt/scrutiny/config'
        environment:
          SCRUTINY_WEB_INFLUXDB_HOST: 'influxdb'
          SCRUTINY_WEB_NOTIFY_URLS:
"pushover://shoutrrr:...@.../?device=iPhone"
        depends_on:
          influxdb:
            condition: service_healthy
        healthcheck:
          test: ["CMD", "curl", "-f",
"http://localhost:8080/api/health"]
          interval: 5s
          timeout: 10s
          retries: 20
          start_period: 10s

    volumes:
      influxdb: {}

I hope someone can push me in the right direction. Thanks a lot!

----------------------------------------------------------------------
thekrautboy · 2023-10-22 19:51

I also use Scrutiny with Pushover and i have this set up in my
`config/scrutiny.yaml`

    notify:
      urls:
        - 'pushover://shoutrrr:APPTOKEN@USERTOKEN'

From a quick search on the Github it appears that those env vars are
not working very reliably, so my suggestion would be to use the config
file instead.

Btw do you really think it makes much sense to set your healtcheck to
20 retries?

      interval: 20s
      timeout: 5s
      retries: 2
      start_period: 30s

More sensible imo.

----------------------------------------------------------------------
thimplicity · 2023-10-22 19:55

When I add the scrutiny yaml file, the connection does not work with
influx anymore. Do you only have the notify information in the yaml?

----------------------------------------------------------------------
thekrautboy · 2023-10-22 19:58

In my compose for web container i have
`SCRUTINY_WEB_INFLUXDB_HOST=scrutiny-influxdb2` where `scrutiny-
influxdb2` is the containername of my influxdb2.

----------------------------------------------------------------------
thimplicity · 2023-10-22 20:11

Would you mind sharing your docker compose and yank content here?

----------------------------------------------------------------------
thekrautboy · 2023-10-22 20:18

version: '2.4'

    networks:
      scrutiny:
        name: scrutiny

    services:

      scrutiny:
        image: ghcr.io/analogj/scrutiny:master-web
        container_name: scrutiny
        restart: unless-stopped
        depends_on:
          scrutiny-influxdb2:
            condition: service_healthy
        networks:
          - scrutiny
        ports:
          - 8116:8080
        environment:
          - SCRUTINY_WEB_INFLUXDB_HOST=scrutiny-influxdb2
        volumes:
          - ./config:/opt/scrutiny/config
        healthcheck:
          test: ["CMD", "curl", "-f",
"http://localhost:8080/api/health"]

      scrutiny-influxdb2:
        container_name: scrutiny-influxdb2
        image: influxdb:2.6.1-alpine
        restart: unless-stopped
        networks:
          - scrutiny
      # ports:
      #   - 8086:8086
        environment:
          - TZ=Europe/Berlin
          - PUID=1000
          - PGID=1000
          - INFLUXD_REPORTING_DISABLED=true
        volumes:
          - ./data/influxdb2_data:/var/lib/influxdb2
          - ./data/influxdb2_config:/etc/influxdb2
        healthcheck:
          test: "wget --no-verbose --tries=1 --spider --no-check-
certificate http://localhost:8086/ping || exit 1"

`config/scrutiny.yaml`

    # Commented Scrutiny Configuration File
    #
    # The default location for this file is
/opt/scrutiny/config/scrutiny.yaml.
    # In some cases to improve clarity default values are specified,
    # uncommented. Other example values are commented out.
    #
    # When this file is parsed by Scrutiny, all configuration file
keys are
    # lowercased automatically. As such, Configuration keys are case-
insensitive,
    # and should be lowercase in this file to be consistent with
usage.


######################################################################
    # Version
    #
    # version specifies the version of this configuration file schema,
not
    # the scrutiny binary. There is only 1 version available at the
moment
    version: 1

    web:
      listen:
        port: 8080
        host: 0.0.0.0

        # if you're using a reverse proxy like apache/nginx, you can
override this value to serve scrutiny on a subpath.
        # eg. http://example.com/scrutiny/* vs http://example.com:8080
        # see docs/TROUBLESHOOTING_REVERSE_PROXY.md
        # basepath: `/scrutiny`
        # leave empty unless behind a path prefixed proxy
        basepath: ''
      database:
        # can also set absolute path here
        location: /opt/scrutiny/config/scrutiny.db
      src:
        # the location on the filesystem where scrutiny javascript +
css is located
        frontend:
          path: /opt/scrutiny/web

      # if you're running influxdb on a different host (or using a
cloud-provider) you'll need to update the host & port below.
      # token, org, bucket are unnecessary for a new InfluxDB
installation, as Scrutiny will automatically run the InfluxDB setup,
      # and store the information in the config file. If you 're re-
using an existing influxdb installation, you'll need to provide
      # the `token`
      influxdb:
        scheme: 'http'
        host: scrutiny-influxdb2
        port: 8086
        #token: ''
        #org: ''
        #bucket: ''
        retention_policy: true
        # if you wish to disable TLS certificate verification,
        # when using self-signed certificates for example,
        # then uncomment the lines below and set
`insecure_skip_verify: true`
        # tls:
        insecure_skip_verify: true

    log:
      file: '' #absolute or relative paths allowed, eg. web.log
      level: WARN


    # Notification "urls" look like the following. For more
information about service specific configuration see
    # Shoutrrr's documentation:
https://containrrr.dev/shoutrrr/services/overview/

    notify:
      urls:
        - 'pushover://shoutrrr:ABC@DEFG'
        - 'smtp://username:password@smtp.gmail.com:587/?FromAddress="u
sername@gmail.com"&ToAddresses="username@gmail.com"&FromName="Scrutiny
"&Subject="Warning"'

    #notify:
    #  urls:
    #    - "discord://token@channel"
    #    -
"telegram://token@telegram?channels=channel-1[,channel-2,...]"
    #    - "pushover://shoutrrr:apiToken@userKey/?priority=1&devices=d
evice1[,device2, ...]"
    #    - "slack://[botname@]token-a/token-b/token-c"
    #    - "smtp://username:password@host:port/?fromAddress=fromAddres
s&toAddresses=recipient1[,recipient2,...]"
    #    - "teams://token-a/token-b/token-c"
    #    - "gotify://gotify-host/token"
    #    - "pushbullet://api-token[/device/#channel/email]"
    #    - "ifttt://key/?events=event1[,event2,...]&value1=value1&valu
e2=value2&value3=value3"
    #    - "mattermost://[username@]mattermost-host/token[/channel]"
    #    - "hangouts://chat.googleapis.com/v1/spaces/FOO/messages?key=
bar&token=baz"
    #    - "zulip://bot-mail:bot-key@zulip-domain/?stream=name-or-
id&topic=name"
    #    - "join://shoutrrr:api-key@join/?devices=device1[,device2,
...][&icon=icon][&title=title]"
    #    - "script:///file/path/on/disk"
    #    - "https://www.example.com/path"

    ##################################################################
######################################################
    # FEATURES COMING SOON
    #
    # The following commented out sections are a preview of additional
configuration options that will be available soon.
    #
    ##################################################################
######################################################

    #limits:
    #  ata:
    #    critical:
    #      error: 10
    #    standard:
    #      error: 20
    #      warn: 10
    #  scsi:
    #    critical: true
    #    standard: true
    #  nvme:
    #    critical: true
    #    standard: true

----------------------------------------------------------------------
thimplicity · 2023-10-22 20:30

Thanks! Will check and try later

----------------------------------------------------------------------
thimplicity · 2023-10-22 23:50

This helped - I got it working - it seems like the only difference
between your setup and mine is that you have both containers in one
network explicitly, while I did not have that. The "fake"
notifications go through. As I lost a disk this week, I hope it takes
a while for the next case.

Thanks a lot!

----------------------------------------------------------------------
thekrautboy · 2023-10-23 02:09

:)

----------------------------------------------------------------------
NewZucchini7081 · 2023-10-25 05:22

Guys, one question about scrutiny. Can i use it with multiple proxmox
hosts and get disk smart values to same dashboard/scrutiny vm? :)

----------------------------------------------------------------------
thimplicity · 2023-10-25 11:12

Yes, that is what I do as well