Raja Subramanian baf47db834 Publish data and signal bytes once every 30 seconds. (#3212) ...

For applications with heavy data usage, accumulating data bytes over 5
minutes and then calculating rate using a much shorter window (like 2 -
5 seconds) makes it looks like there is a massive rate spike.

While this change is not a fix, this should soften the impact.

Need a better way to handle different parts of the system operating at
different frequencies. Can use rate in the reporting window, but that
will miss the spikes. Maybe that is okay. For example, if the reporting
window is 5 minutes and there was a 100 Mbps spike for about 10 seconds
of it, it would get smoothed out.

2024-11-28 09:21:44 +05:30

..

prometheus

De-centralize some configs to where they are used. (#3162)

2024-11-08 12:47:30 +05:30

telemetryfakes

Analytics: send local node room state/info (#2335)

2023-12-22 18:59:04 -05:00

analyticsservice.go

Some misc clean up. (#3156)

2024-11-04 11:26:41 +05:30

events_test.go

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

events.go

Attempt to fix missing participant left webhook. (#3173)

2024-11-14 10:59:15 +05:30

signalanddatastats.go

De-centralize some configs to where they are used. (#3162)

2024-11-08 12:47:30 +05:30

stats_test.go

get cpu stats from cgroup, remove env (#2636)

2024-04-08 21:15:17 -07:00

stats.go

Record out-of-packet count/rate in prom. (#2980)

2024-09-07 00:19:54 +05:30

statsconn.go

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

statsworker.go

replace proto.Clone calls (#3024)

2024-09-18 22:47:33 -07:00

telemetryservice.go

Publish data and signal bytes once every 30 seconds. (#3212)

2024-11-28 09:21:44 +05:30