Laremere
Laremere
I currently don't see much request for this. Please chime in if this is something you want.
Hey Adam, thanks for looking into this. I will note that I'm not familiar with how all of the helm stuff was set up, and think it's a likely source...
Yes, that would be preferable.
We don't recommend using match function invocations per server for backfill (I know it was the suggestion at one point, but we've since changed it). We have a separate issue...
I think what I meant to say was one for the demo, fixed. I specifically don't want a "use this chart for your match function" because we don't know what...
Multiple fetch match calls will use the same evaluator, which is why it isn't specified in the call. The tags suggestion is interesting. I'm always for reducing complexity. Speaking, I'm...
There's some problems with the config being generated as well: - Resources for the different services should be more independently controllable, as eg the synchronizer commonly has higher load and...
Yeah, that's a pretty obvious change now that you mention it. We should probably do the same with the standard demo as well.
Yufan, please provide your prototype for this working, and any other findings you haven't documented yet. Thanks!
I see a few general approaches to a stats API: 1. Raw column extractor 2. Bucketing 3. Population division Example data: ticket ID: rank, name, latency T1: 15, foo, 103ms...