logcli: adds --analyize-labels to logcli series command and changes how labels are provided to the command

[slim-bean]

Changes the series command to use the common matcher input found in the query and instant-query commands, instead of logcli series --matcher='{foo="bar"}' it's now logcli series '{foo="bar"}'

Adds --analyze-labels which prodcues output like this:

Total Streams:  25017
Unique Labels:  8

Label Name  Unique Values  Found In Streams
requestId   24653          24979
logStream   1194           25016
logGroup    140            25016
accountId   13             25016
logger      1              25017
source      1              25016
transport   1              25017
format      1              25017

For debugging high cardinality labels

[codecov-commenter]

Codecov Report

Merging #2497 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2497   +/-   ##
=======================================
  Coverage   63.22%   63.22%           
=======================================
  Files         162      162           
  Lines       14115    14115           
=======================================
  Hits         8924     8924           
  Misses       4484     4484           
  Partials      707      707           

[owen-d]

I thin this should continue to take a slice of match clauses, but LGTM asides that.

[owen-d]

This should take a slice of matcher clauses, see https://grafana.com/docs/loki/latest/api/#series

[slim-bean]

i debated this but honestly I couldn't figure out why that would be useful? I couldn't think of a usecase for this from logcli? I may totally be missing one though.

[owen-d]

It's probably ok. I think this is more important for Prometheus which can't combine multiple metric names in the same matcher clause, but loki doesn't have this problem.

Anyways, we can always add it in the future if there's a case where we need it. LGTM

[cyriltovena]

I love this PR.

[ruanbekker]

--analyze-labels is really neat. It was quite quick to see how many unique labels / total streams per job, in a scripty way:

for label_value in $(logcli labels job); 
do 
  echo "==> job=\"$label_value\""; 
  logcli series '{job="'"$label_value"'"}' --analyze-labels ; 
done

Unless there's a query to do ^ :-D