-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 Packages #52
Comments
+1. Packages for promtail and Loki. |
This could be very useful when hitting (at least) an alpha release. |
more than packages ; alpha release on github would be handy; then we can packge it ourselves. |
We'll start with releases in late May when Loki goes into Beta. |
Windows binaries too please (since those are always much more of a pain to build) |
try to build on 1GB RAM vps , but it always panic with OOM |
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. |
@DanCech I believe this issue can be closed now. |
I will work on this soonish. I might create rpm first also I might be that I could build Debian pkg (if needed) with obs https://openbuildservice.org/ We do already for other projects |
My plan would be to pkg promtail and loki in different pkgs and create a systemd service to start stop agents. As a question what do you think about the configuration files directory?? Where should we put conf? E.g in existing etc/grafana or etc/loki and etc/promtail ? |
I'm rooting for etc/loki and etc/promtail |
ok thx! sounds good to me |
1 similar comment
ok thx! sounds good to me |
ok first RPM I have build for opensuse are here 🍏 https://build.opensuse.org/package/show/server:monitoring/loki. I will need to play and experiment with this pkg and then I could update the pkgs to 0.3.0. Currenlty I have some issues with the golang pkg. I guess perhaps soemthing changed in the vendoring? orsoemthing between 0.1.0 to 0.2.0 I might neeed to check. After that, I could investigate to provide pkgs for other distros |
Are there any Debian packages available yet, or does that still need to be built out? |
We’re looking for help for debian. |
just for future reference, the correct link ended up being https://build.opensuse.org/package/show/security:logging/loki |
The Grafana Cloud Agent, which embeds promtail, does have packaging: https://github.com/grafana/agent/tree/master/packaging This could be a good alternative. |
In reference to "Go add a comment to that issue for which package managers you would like." from #3119 I think you can cast a really wide net with deb and rpm. |
Can jump in here...but i would not walk the hard way creating the debian package myself but using fpm instead. I'm using this for countless projects. |
There is already a guy generating deb packages automatically in this project https://github.com/growse/promtail-package/ maybe you can take a look a what he does |
Looks like fpm ;) Good job! |
Hi! That's me! Yes, just fpm. I host the result on my own apt repo, I should try and get round to adding the debs to github releases as well. I also need to double-check the way in which they're getting built, because I've got this issue on arm: #3406 and I'm not sure if it's an issue with the code, or the build settings. More work needed... |
You can easily use Gitlab Pages for a repo ;) https://morph027.gitlab.io/blog/repo-hosting-using-gitlab-pages/ |
Ah, interesting. As the README says, I currently host the packages on my own apt repo (https://apttoo.growse.com/). I should probably put Cloudflare or something in front of it in case lots of people suddenly start using it... |
This is a great idea. We predominantly use Debian/Ubuntu and CentOS/Alma in our environment, so the following three package managers would be handy to support, and would cover off most needs, I'd say:
This may warrant a separate issue, but at least providing the Linux binaries in a |
@growse the https://apttoo.growse.com/ url isn't opening now with "Unable to connect" error, is this a temporary problem now with it? |
Also we can use launchpad.net to publish repos with downloadable packages. |
It is IPv6 only, so I guess you're trying to connect over IPv4? |
Yeah I'm having the same problem as well. Sadly most of the ISPs in my country only give ipv4. |
For IPv4-only environment, you may try to setup 6to4 so that you can connect to IPv6-only resources. btw, well, I also have built loki & promtail binaries (deb) in Launchpad PPA as well: It's a minimal package (only binaries), so you need to configure other things (e.g. systemd service files) yourself. |
FYI we package promtail (and the rest of loki) in ArchLinux: https://archlinux.org/packages/community/x86_64/promtail/ |
Debian needs official promtail and loki packages so we can get security patches and start stop with systemd. There is already for grafana https://grafana.com/docs/grafana/next/setup-grafana/installation/debian/. Anyone is working on this? @MalloZup @cyriltovena @davkal |
There is a POC #6456 |
**What this PR does / why we need it**: With #6456 we started providing native packages of Loki, Promtail and logcli. They've been added to Grafana's repository in the meantime. In order to spread the knowledge of the packages and the repo it should be documented. **Which issue(s) this PR fixes**: Fixes #52 **Checklist** - [ ] Reviewed the [`CONTRIBUTING.md`](https://github.com/grafana/loki/blob/main/CONTRIBUTING.md) guide (**required**) - [x] Documentation added - [ ] Tests updated - [ ] `CHANGELOG.md` updated - [ ] Changes that require user attention or interaction to upgrade are documented in `docs/sources/upgrading/_index.md` --------- Co-authored-by: René Scheibe <[email protected]> Co-authored-by: J Stickler <[email protected]>
Currently we don't have an easy way for anyone wanting to use standalone promtail to install it as a service on their host machine(s).
We should at least provide pre-built binaries, and ideally packages that can set up the services to run it at boot.
For starters we should provide .deb and .rpm packages.
The text was updated successfully, but these errors were encountered: