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

Promtail: Add scrape_config to accept unstructured logs via HTTP #4316

Closed
ldb opened this issue Sep 13, 2021 · 1 comment · Fixed by #4336
Closed

Promtail: Add scrape_config to accept unstructured logs via HTTP #4316

ldb opened this issue Sep 13, 2021 · 1 comment · Fixed by #4336
Labels
component/promtail type/enhancement Something existing could be improved

Comments

@ldb
Copy link
Contributor

ldb commented Sep 13, 2021

Is your feature request related to a problem? Please describe.
At the moment there is a way to send 'unstructured' (in the sense of schemaless) logs to Loki via the STDIN scrape_config in Promtail. Structured logs can be sent to Loki using the loki_push_api scrape_config using HTTP. We propose to add a similar feature that accepts unstructured logs via HTTP similar to the STDIN way. This enables a set of new integrations such as with Vercel Log Drains for sending logs via HTTP.

Describe the solution you'd like
Add a scrape_config to accept generic logs via HTTP.

Describe alternatives you've considered
Other ways of connecting cloud services to Promtail, which usually involve writing custom glue code to accept logs via HTTP only to pipe them into Promtail.

Additional context

@aengusrooneygrafana aengusrooneygrafana added component/promtail type/enhancement Something existing could be improved labels Sep 13, 2021
@aengusrooneygrafana
Copy link
Contributor

Hi Leo, thanks for submitting this - as discussed, we'll check in with @cyriltovena to get his 👀 on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/promtail type/enhancement Something existing could be improved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants