Simple monitoring solution
Go to file
2024-06-01 09:01:58 +02:00
notification View datapoint values 2024-05-05 21:06:31 +02:00
sql Added nodata notification 2024-05-27 23:01:34 +02:00
static Index page UI adjustment 2024-06-01 09:01:58 +02:00
views Index page UI adjustment 2024-06-01 09:01:58 +02:00
.gitignore Initial commit 2024-04-29 08:36:13 +02:00
area.go Fixed problems with empty tables, bumped to v4 2024-05-01 21:44:53 +02:00
config.go Configurable interval for nodata checks 2024-05-30 13:31:51 +02:00
datapoint.go Don't erase datapoints when used in triggers. 2024-05-30 13:32:04 +02:00
go.mod nodata ui changes 2024-05-25 15:00:01 +02:00
go.sum nodata ui changes 2024-05-25 15:00:01 +02:00
main.go Bumped to v16 2024-05-30 15:06:57 +02:00
nodata.go Configurable interval for nodata checks 2024-05-30 13:31:51 +02:00
notification_log.go View datapoint values 2024-05-05 21:06:31 +02:00
notification_manager.go Nicer notification manager initialization 2024-05-05 10:12:21 +02:00
page.go Adding datapoints to triggers 2024-05-01 10:02:33 +02:00
problem.go Show NODATA problems in UI 2024-05-28 07:23:27 +02:00
README.md Updated config example 2024-05-30 17:22:38 +02:00
section.go Implemented adding/renaming of areas and sections 2024-05-01 21:02:45 +02:00
trigger.go Better trigger create 2024-05-30 15:06:41 +02:00

Quick start

  1. Create an empty database
  2. Create the configuration file (default ~/.config/smon.yaml)
  3. Run ./smon (will create the database schema)

Configuration

network:
  address: "[::]"
  port: 9000

websocket:
  domains:
    - localhost
    - smon.example.com

database:
  host: localhost
  port: 5432
  name: smon
  username: smon
  password: you_wish

session:
  daysvalid: 31

application:
  logfile: /var/log/smon.log
  nodata_interval: 60

Data from systems to datapoints

curl -d "$(time +'%F %T +02')" http://localhost:9000/entry/datapoint_name