Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs missing vital information #15182

Open
jenia opened this issue Nov 28, 2024 · 0 comments
Open

Docs missing vital information #15182

jenia opened this issue Nov 28, 2024 · 0 comments
Assignees
Labels
area/helm type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Comments

@jenia
Copy link

jenia commented Nov 28, 2024

Describe the bug
Docs examples missing vital information

To Reproduce
Steps to reproduce the behavior:

  1. Install Loki in monolith mode using Helm charts following these docs.
  2. See these type of errors: {"time": "2024-11-28T14:57:41.907260+00:00", "taskName": null, "msg": "5xx response content will not be enabled.", "level": "INFO"} at least one bucket name must be specified github.com/grafana/loki/v3/pkg/storage/chunk/client/aws.buckets
  3. Realize that you need to also configure both the storage and storage_config values:
loki:
  storage:
    bucketNames:
      chunks: "abc"
      admin: "def"
      ruler: "ghi"

loki:
  storage_config:
    gcs:
      bucket_name: "abc" <----- notice it's same as chunks above... I don't know why but seems to work
      service_account: |
        {
         ...
        }

shown here and here respectively.

Expected behavior
Complete example of how to setup a monolith Loki instance using Helm.

Environment:

  • Kubernetes
  • Helm

Screenshots, Promtail config, or terminal output
N/A

Can someone please also explain, what does the

loki:
  storage_config:
    gcs:
      bucket_name: "abc" <----- notice it's same as chunks above... I don't know why but seems to work

do? Why do you need to specify that bucket twice?

Thanks kindly for updating the docs with full, working examples.

@JStickler JStickler added area/helm type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories labels Dec 2, 2024
@JStickler JStickler self-assigned this Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

No branches or pull requests

2 participants