Server Metrics Reporting #41

New Issue

sarah · 2018-06-13T01:05:15Z

sarah commented

2018-06-13 01:05:15 +00:00

A server admin should be able to know:

RAM Usage
Disk Usage
Number of Connected Clients
Historical Use

Sending these as a GroupMessage would be cool:

Admin configures a cwtch id in server.config
Server loads config, finds cwtch id and attempts to connect
Once they have connected, server sends a group invite (referencing it's own server id)
User accepts group invite, connects to server and now gets stats updates every period of time

Later on we could add configuration to happen through that channel too.

A server admin should be able to know: * RAM Usage * Disk Usage * Number of Connected Clients * Historical Use Sending these as a GroupMessage would be cool: * Admin configures a cwtch id in server.config * Server loads config, finds cwtch id and attempts to connect * Once they have connected, server sends a group invite (referencing it's own server id) * User accepts group invite, connects to server and now gets stats updates every period of time Later on we could add configuration to happen through that channel too.

dan commented

2018-06-20 06:32:33 +00:00

messages per time period
all the rest per time period

- messages per time period - all the rest per time period

dan commented

2018-06-29 21:48:38 +00:00

metrics gathering and reporting to local file is done with #73, #72, and #69

do we want to break off reporting to a group to another task or leave this open?

metrics gathering and reporting to local file is done with #73, #72, and #69 do we want to break off reporting to a group to another task or leave this open?

sarah commented

2018-06-29 21:53:36 +00:00

Let's close this for now, I want to think about the design more per our conversation the other day.

sarah closed this issue

2018-06-29 21:53:36 +00:00

Sign in to join this conversation.