[09:28:05] <godog>	 tomorrow's pad is up!
[09:30:23] <volans>	 thx
[11:36:12] <jynus>	 what is a good generic name for what prometheus holds for our infra? time-based metrics? (vs alerting) how do you call that service?
[11:40:18] <volans>	 technically monitoring, as the icinga side is alerting, an even more generic observability, but has much more in it
[11:40:31] <volans>	 but I understand if you don't want to use monitoring because feel confusing
[11:41:01] <volans>	 metrics might be another one, a bit meh though
[11:42:17] <jynus>	 I think I may end up calling it prometheus to avoid ambiguity (if we happen to move to some other model, documentation will be deprecated anyway)
[11:49:44] <paravoid>	 time-series database is the underlying tech, "metrics-based monitoring" or "metrics infrastructure" is what I'd call the product offering
[12:13:33] <jynus>	 thanks, paravoid
[14:22:43] <paravoid>	 I'd like to talk annual planning tomorrow at our meeting
[14:22:56] <paravoid>	 please do add items to the roadmap spreadsheet
[14:23:04] <paravoid>	 it's currently very empty
[14:23:49] <paravoid>	 please at least put broad themes an ideas in by tomorrow
[14:30:23] <volans>	 ack
[15:08:07] <paravoid>	 we can maybe use the bolding technique to discuss some of these more extensively during our meeting, how does that sound?
[15:11:04] <moritzm>	 sounds good to me
[15:11:07] <volans>	 +1
[15:13:25] <godog>	 same here
[15:15:29] <cdanis>	 I won't be able to attend, but will try to find some time today to add ideas