armin/linspector
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

.gitignore and README update.

Browse source
This commit is contained in:
Johannes Findeisen 2023-02-21 02:33:39 +01:00
commit 41047b743a
3 changed files with 13 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

18
files/mariadb.sql
View file

@ -7,14 +7,14 @@ DROP TABLE IF EXISTS log;
CREATE TABLE log (
-- maybe do not use a autoincrement field because of limits. maybe just index more fields. since there is no
-- relation to other tables a primary key makes no sense.
id BIGINT UNSIGNED AUTO_INCREMENT, -- maybe this could be the monitor id because they are unique and will not change after restart
date date, -- current date
time time, -- current time
timestamp timestamp, -- execution timestamp returned from the monitor's service (last_execution)
id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT UNIQUE,
_date date, -- current date
_time time, -- current time
_timestamp timestamp, -- execution timestamp returned from the monitor's service (last_execution)
status VARCHAR(5), -- NONE, OK, ERROR (maybe assign number to the codes for fast database searches?)
message VARCHAR(255), -- a short message returned by each monitor (max 255?)
monitor VARCHAR(255),
monitor_args LONGTEXT, -- kwargs passed to the monitor's service
monitor_args VARCHAR(255), -- kwargs passed to the monitor's service
monitor_id VARCHAR(64),
service VARCHAR(255),
job_id VARCHAR(32),
@ -22,7 +22,9 @@ CREATE TABLE log (
host VARCHAR(255),
hostgroups VARCHAR(255),
job_threshold INT(128),
raw LONGTEXT, -- raw json response data from a monitor's service. maybe write this data to a different database optimized for json object storage and use the monitor_id for relation.
PRIMARY KEY(id, monitor_id),
INDEX monitor_id(monitor_id)
raw LONGTEXT, -- raw json response data from a monitor's service. maybe write this data to a different database optimized for json object storage and use the id for relation.
PRIMARY KEY(id, _timestamp, monitor_id),
UNIQUE INDEX (id),
INDEX monitor_id(monitor_id),
INDEX _timestamp(_timestamp)
);