Conversation
Co-authored-by: Megrez Lu <lujiajing1126@gmail.com>
…ta-dev/krr into prometheus-workload-loader
|
When testing using the prometheus mode on a centralized Prometheus (VictoriaMetrics), I encountered the following errors.
To me it seems that the query includes the wrong label here, and should be |
The name is misleading. Before this change we had both --prometheus-cluster-label and --prometheus-label which referred to very different things, leading to a bug in the code (to be fixed in the next commit). We still support -l and have added support for "--prometheus-cluster-value" which is what `-l` really represents.
|
|
||
| ```sh | ||
| krr.py simple --prometheus-label cluster -l my-cluster-name | ||
| krr.py simple --prometheus-cluster-key cluster -l my-cluster-name |
There was a problem hiding this comment.
@arikalon1 it should be fine. I'm not deprecating --prometheus-label, just adding another option with a name that makes more sense.
I did deprecate --prometheus-cluster-label but the runner doesn't pass that by default.
| prometheus_cluster_label: Optional[str] = typer.Option( | ||
| None, | ||
| "--prometheus-cluster-label", | ||
| "--prometheus-cluster-value", |
There was a problem hiding this comment.
Yes, this one I did change but if I understand the runner code correctly, it uses -l which is still supported and equivalent to this flag. So no change needed.
|
Hi @deutschj, |
|
@deutschj please note that I changed the name of the flags a little -- see |
|
@aantn Sure, thanks a lot for working on the bugfix! Whett testing with the options However, when providing only the And the table with the generated resource recommendations in the end is empty though. |
|
@deutschj does it work if you provide |
|
@aantn Unfortunately not, no - this yields the same error as above, |
|
Would love to see this merged, using KRR from this feature branch for some time now |
|
Hey, we're planning to get it merged, but no exact ETA yet. |
|
hello. Are there any plans for this branch to be merged? |
|
hey @wad-hongsumin We do plan to merge it, hopefully soon |
|
@arikalon1 |
|
is it possible to divide MR into several MR? |

Testing issues found: