Loki: [Better] "Getting started" guide

Created on 12 Dec 2019  路  7Comments  路  Source: grafana/loki

I tried this once before (out of curiosity, liking Prometheus, Grafana and Jsonnet).

I returned again but I am again admitting defeat :-(

I'm submitting this issue, in case I'm representative of other developers who struggle with this.

Is there a definitive, working "Getting start" guide that goes from having a Kubernetes cluster to a working example? Should I use the Helm deployment rather than Tanka?

This recommended (!) approach appears insufficient and incorrect:
https://github.com/grafana/loki/blob/master/docs/installation/tanka.md

Issues:

There's little explanation of the goal and how the steps contribute to this.

I assume we need Loki running to aggregate logs, at least one promtail (agent) to gather logs and some application (configured) to ship logs caught by promtail into Loki that can be viewed in Grafana.

After muddling through the instruction, I receive (unexpected) errors about Bigtable:

tk status environments/loki
evaluating jsonnet: RUNTIME ERROR: must specify bigtable instance
    .../loki/vendor/loki/config.libsonnet:21:24-62  object <anonymous>
    .../loki/vendor/loki/config.libsonnet:74:19-46  object <anonymous>
    .../loki/vendor/ksonnet-util/kausal.libsonnet:391:9-28  builtin function <toString>
    .../loki/vendor/ksonnet-util/kausal.libsonnet:391:7-29  function <anonymous>
    .../loki/vendor/loki/config.libsonnet:234:22-57 object <anonymous>
    During manifestation
componenpackaging good first issue help wanted keepalive stale

Most helpful comment

Totally agree with @DazWilkin ... I get the same error with tk.
Just copying&pasting commands without knowing what and why I am doing that.

All 7 comments

I tried the Helm instructions. These work flawlessly!

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

Totally agree with @DazWilkin ... I get the same error with tk.
Just copying&pasting commands without knowing what and why I am doing that.

I'm also experiencing the same error when using Tanka. I'm trying to use tk export so that I can use raw yaml files. Is there a way we can ignore this error?

got the same error

the same for me also, and this case seams not to be closed ....also with helm i have some problems....the health check on the loki testing pod is failing....and i don't now why... so i went to tanka...just to get this issue...

I get the same errors as well. Just trying to get example YAMLs of production setup on system. The all-in-one helm setup works great. Have not found any clear documentation on how to setup production.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

oleksandr-hyuna picture oleksandr-hyuna  路  4Comments

negbie picture negbie  路  3Comments

bzon picture bzon  路  5Comments

suppix picture suppix  路  3Comments

ghostsquad picture ghostsquad  路  3Comments