|
avoid counters imo
|
#
¿
Feb 23, 2019 13:42
|
|
|
|
| # ¿ May 14, 2024 01:55 |
|
|
pram posted:kafka is about 1000x times shittier so count your blessings kafka is extremely good, maybe your just holding it wrong
|
|
#
¿
Mar 8, 2019 09:41
|
|
|
works fine on my machine(s)
|
|
#
¿
Mar 9, 2019 06:35
|
|
|
pram posted:if you run multi-tenant clusters where people are doing compaction and exactly-once and theres 10000 different consumer groups then its a total shitshow Progressive JPEG posted:maybe your just holding it wrong
|
|
#
¿
Mar 9, 2019 11:10
|
|
|
please watch these broken dashboards/alerts, and absolutely never under any circumstances fix any problems you find maybe ask manager why they aren't empowering you to maintain the things you depend on to do your job
|
|
#
¿
Mar 16, 2019 21:48
|
|
|
datadog gets very sad if you have lots of tags/cardinality
|
|
#
¿
Jul 8, 2019 09:43
|
|
|
the code that's writing the log should also be writing to a database efb
|
|
#
¿
Jul 22, 2020 19:10
|
|
|
Pardot posted:i want to send structured logs/events at some service that I wont have to janitor. the events will mostly be an entity with one or more uuids, and then some info like state changes, maybe some timestmaps or durations, idk. Nothing automated needs to consume this, just sometimes a person will do a search on the uuids to figure out what happened. I only need like 7 maybe 14 days of retention and the volume of incoming events wont be so high. Probably like 1gb/day, for sure less than 100. Only like 5 people will need access. given just a gigabyte a day and only occasional use, it could honestly just be a set of hourly text files with regular backups that they would grep if you're feeling fancy then write as a gzip stream and tell them to use zgrep
|
|
#
¿
Jul 29, 2020 08:43
|
|
|
|
| # ¿ May 14, 2024 01:55 |
|
|
which mutually incompatible version of influxdb did you go with
|
|
#
¿
Feb 12, 2024 12:52
|
|