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

Grafana alloy not pushing all the self logs to loki #1225

Open
ashwinisivakumar opened this issue Jul 8, 2024 · 1 comment
Open

Grafana alloy not pushing all the self logs to loki #1225

ashwinisivakumar opened this issue Jul 8, 2024 · 1 comment
Labels
bug Something isn't working needs-attention

Comments

@ashwinisivakumar
Copy link

ashwinisivakumar commented Jul 8, 2024

What's wrong?

we are using below config to push Alloy logs to Loki, observing some log lines are missing.

level = "info"
format = "logfmt"
write_to = [loki.write.cloud_loki_ent.receiver]
}
However if we use scrape config to scrape the logs lines from a file, all the log lines are getting pushed into Loki

Steps to reproduce

Run the Grafana alloy with self logs scrape.

System information

No response

Software version

Grafana Alloy v1.0.0

Configuration

logging {
      level  = "info"
      format = "logfmt"
      write_to = [loki.write.cloud_loki_ent.receiver]
    }
   
    loki.write "cloud_loki_ent" {
      endpoint {
        url        = ""
        batch_wait = "10s"
        tenant_id  = ""
        min_backoff_period = "500ms"
        max_backoff_period = "5m"
        max_backoff_retries = 10
       
      }
      external_labels = {

      }
    }

Logs

No response

@ashwinisivakumar ashwinisivakumar added the bug Something isn't working label Jul 8, 2024
Copy link
Contributor

github-actions bot commented Aug 8, 2024

This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-attention
Projects
None yet
Development

No branches or pull requests

1 participant