monolith-network monolith issues

monolith-network / monolith

Telemetry command and control server

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Accounting

#30 bosley opened 2 years ago
1
Add telnet to monolith

#29 bosley closed 2 years ago
0
Weather station dev

#28 bosley closed 2 years ago
0
In the portal, and maybe with an app, make a command interface so we can send commands like "reload lua file" and stuff like that

#27 bosley closed 2 years ago
2
7 rollup

#26 bosley closed 2 years ago
0
18 Remove direct TCP data submission

#25 bosley closed 2 years ago
0
Convert Monolith to using HTTPS

#24 bosley opened 2 years ago
1
CI/CD Pipeline - Write a series of tests in python that ensures monolith is doing what it should be

#23 bosley opened 2 years ago
0
"account" out all http endpoints by prefixing all of them with `/< account id >` and make is so each account has their own distinct registrar and metric database. To verify accounts, a rekdb could be setup and run in conjunction with monolith that handles known accounts and license info.

#22 bosley closed 2 years ago
4
15 actions

#21 bosley closed 2 years ago
0
17 versioning endpoint

#20 bosley closed 2 years ago
0
Unregistered nodes may still have data in the database. Add something like `/maintenance/clean` that will remove all entries from the database from nodes that are no longer registered

#19 bosley opened 2 years ago
0
In `monolith` consider stripping out the nettle server from `data_submisison` and have data submission be HTTP only - this will take a thread out of the mix

#18 bosley closed 2 years ago
0
Add a way to get the commit hash in monolith and add a `/version` endpoint that gives the commit, build date, version, etc

#17 bosley closed 2 years ago
0
Create `/metircs/purge/<node-id>` that removes all submitted metrics by that node's sensor(s), and `/metrics/update/<node-id>/add/<encoded-sensor>` / `/metrics/update/<node-id>/delete/<sensor-id>`

#16 bosley opened 2 years ago
0
Extend lua functions so "actions" can be triggered - Need to register actions/controllers with the registrar or something so we can have

#15 bosley closed 2 years ago
0
configurable alerts

#14 bosley closed 2 years ago
0
Convert twilio backend to use httplib and not curl so we can remove curl as a depends

#13 bosley opened 2 years ago
0
Modify alerts to take in from config an ant-spam cooldown time & max_sends limit

#12 bosley closed 2 years ago
0
sms alerts working

#11 bosley closed 2 years ago
0
working towards twilio integration

#10 bosley closed 2 years ago
0
Using the script stuff developed in the task prior, write a series of tests that ensure all http endpoints work the way they promise to as-per the docs (registrar/submission/database access etc)

#9 bosley opened 2 years ago
0
Wrap up crate in python or lua or something... maybe write a python library? Something that we can use to script monolith and monolith access. Perhaps a "main" that takes in a lua script and sets up a lua environment to mess with services and also adds access to crate?

#8 bosley opened 2 years ago
0
Database Rollups

#7 bosley closed 2 years ago
1
Start `rule manager` get it taking in metric streams directly (not over http/tcp). Once initial framework is setup begin figuring out how the language will work that is used to configure it.

#6 bosley closed 2 years ago
1
Monolith Unit Testing

#5 bosley closed 2 years ago
0
start `portal` service to serve as a simple node / controller manual input page

#4 bosley closed 2 years ago
1
Create `alive` manifest service, `crate::sensors::heartbeat` encode/decode and update `device_emulator` to send out heartbeats

#3 bosley closed 2 years ago
0
Finish DB implementation

#2 bosley closed 2 years ago
3
Modify Monoloth

#1 bosley closed 2 years ago
0