I've tried graylog, elk, datadog, cloud watch and a few others. Most are overkill, some are crazy expensive and none are perfect (or even great) Loki was on the 'check out at some point' list
These guides are insane. No one goes to the detail that you do. You explain why and how commands and config files work rather that just reading them. Love your channel!
Great tutorial! One thing to note if you want to log specific docker containers you don't need to install promtail or change the deamon file. Just need the docker plugin for Loki and extra configuration in docker-compose for your specific containers that should use dedicated Loki logging driver.
I've watched so many deployment videos trying to get a better all around understanding on all the NMS out there, what they can do, how they operate under the hood, etc. This by far is the absolute best I have seen and definitely earned you a sub. Most deployment videos tend to be quite dry, very un-explainative, and usually feel like a 'just do this real quick and it works' video. Thank you!!!
Hi Tim, you look like the kind of guy to keep (their system) up to date, but for those that may not know, there was a high-severity, zero-day vulnerability for Grafana a few days ago that enabled remote access to local files. Anybody that could access the site could access any file on the system, like for instance /etc/passwd. There are proof-of-concepts publicly available so it takes hardly any skill for script kiddies to start scanning. Grafana released a fix right away. If you have not already, install the latest versions / patches!
+1 I've noticed this as well, but by using the "latest" tag the fixed version should be pulled next time you up the containers with the "--build" argument. Just want to add a small note for others as well, that using "latest" is not a best practice, and you should specify the version you want to use (especially in production), else you could end up pulling a vulnerable version without even realizing.
Excellent! I am a long time user of Grafana and do a lot with it, but now the job is to manage the logs: here we are! Loki is the tool we want to deploy. Thanks a lot for your video, brillant, will be very helpful!
Yo bro, I like your video and the way explained every single bit and steps are just beyond awesome. Thanks for this quality content. God bless you my friend.
I was waiting for this video. Very well explained as always, thanks Tim ! To take a quick glance at my docker logs, i like to use Dozzle, a very small and straight to the point tool, but it does the job
Fantastic tutorial... everything explained really well, and worked perfectly.. great way to get up and running with Loki / Promtail / Grafana quickly!!
You know it's like really simple to develop plugins for Grafana? In my recent job we had to develop some very custom dashboards on the data we were collecting and it turns out Grafana has this whole eco-system to develop not only panel plugins, or data source plugins, but even app plugins, which integrate directly into the Grafana UI. It's really nice, since you get all user management and auto-reloading of data mechanisms for free :) And when I say easy, I mean really hard if you don't know it's basically React (and I didn't know React). But once you figure it out, it's easy.
It was an interesting video though, I had been wondering about this logging stack for a while and if I should chase it. The thing is, Kibana is just too powerful. Like even having unstructured data and being able to structure it on the fly is just everything.
Loki is great, very versatile. Be warned tho if you have limited storage space the loki database can grow in size quick! Edit: loki doesn't trim old logs by default.. I only keep logs up to two weeks old. Huge data saver!
What config items do you need to set to change the default storage locations? I'm looking at their config reference and having trouble making sense of it
Messing with influxdb but will check out Loki next. Wondering how Loki performs with TBs of logs without switching to cloud storage. Thanks for the video!
You can't start logging this professional now dude, I stayed hidden so far from you but now it's impossible 🤣 You have so many docker tutorials and you're actuality running them in your house that... I have to... I hereby declare you the docker King of RUclips!
The docker loki plugin had a serious problem, so it was not an option for production use. I don´ t know if this issue has been solved. The last time I was reading through the related issues the developers said, that they might not be able to provide a solution anytime soon. Let me describe: If your container host has high IO load and/or the loki server is not reachable for some reason the whole docker daemon hang up, because it wasn´t able to write the logs. The worst possible situation is when shutting down multiple containers. It wasn´ t possible to define some timeout. It was required to kill the daemon process and remove the container files (/var/lib/docker/containers) the daemon normally manages. I never used the plugin again. I´m happy with configuring the log property of a container and have promtail to scrape this. The result is the same, but without the possibility of a blocked daemon.
i usually do Elasticsearch, i know its heavy in use and maintenance but also plugs into other things like my wiki so its great. Loki does look promising tho.
for the syslog, see if you can point the logs towards a dummy ip address. this way if someone gets into you system, they won't be able to find and mess with the logging server
Can this be used in a closed source commercial product? The AGPL license is concerning. Even though no changes are made to the source code, and it would only be used for internal purposes, section 13 of the license is concerning. The software is a web application, so it would be accessible over a network, and while logs would obviously not be shown to end users, and technically aren't even necessary for the application to work, they are necessary for development and debugging.. Can't figure out whether it can be used in my company or not
Tried Loki, because it's easy to correlate it with Jaeger so you could check out traces based on trace ids found in logs. But to have advanced features on your logs, there's nothing else like elk+kibana. It only depends on what your needs are. Cheers and thumbs up for your videos ;) keep up the good work!
Hi! Before all, amazing video!! But, I'm having an issue when I try to do the first query, I see "No logs volume available". I already checked /ready and /metrics and looks good. Do you know which can be the problem? Thanks a lot
Used graylog for a while, hated it. This looks much nicer, going to give it a whirl. Currently just aggregating into a rsyslog server with some scripts to compress and logrotate.
Hey Tim, great content as per usual!! I just saw your video and been struggling to set up logging from a firewall with this especially since promtail will be deprecated next year and they are switching to alloy. I wanted to know what are you using today in 2024 and if your still use this setup, have you migrated to alloy instead ?
I swear software is annoying. If you look at the official docs to install this thing using docker-compose there's no mention of most of what Tim talks about. "Creake a loki folder and run this wget. Done." And if you look at the yaml file from the repo it's completely different than Tim's. If software developers knew how to communicate they'd be dangerous.
excellent, man! We are evaluating right now a custom logging solution as the ones offered by major cloud providers are quite expensive... alternatives would have been an ELK stack, or something preconfigured as graylog... what do you think? Thanks
really depends on your infra! This is great for cloud, containers, kuerbernetes, and even traditional syslog. If you are already sing grafana that's a plus too!
Great video, I have a question about the promtail adding docker section. when you set up the docker loki driver, the daemon config was sending logs directly to loki so I am not sure what the promtail configuration actually did in this setup. Additionally, the promtail config was set to push from /var/lib/containers.... but this would have ben for the folder within the container of promtail only and not host. Have I missunderstood something?
You are correct, I believe the loki driver method is completely different form the promtail one with the docker pipeline stage See the other comment I just posted about this for more details :)
1. Is Loki-Promtail stack suitable for aggregating and shipping logs that are generated at microsecond level?. 2. When logs are available in multiple files, promtail ships the logs in round robin fashion, spoiling the order of the logs. (Let's say logs generated through rolling file appender fashion). Any comments will be helpful.
Great video! I installed grafana, prometheus, loki and promtail on my Proxmox host and I am really liking it. One question: is there an easy way to get promtail to get logs from my Proxmox LXC containers and VMs? Or do I need to install promtail into each LXC/VM in order to get the logs into loki?
Awesome video @TechnoTim . Around the 15:24 mark, he was talking about how you would usually check Docker logs then scrolled down his container names, how did he do that? I'm assuming it is a particular shell, maybe? Anyone knows?
I seem to be missing something with the syslog portion. I set it up with the listening ports. I then went into one of my network devices and pointed it to loki on port 1514. Now what? I don't see anything in grafana indicating that any syslogs are coming in. I must be missing something really basic.
Yeah, that installs prometheus, grafana, alert manager, and everything to log and alert for an entire cluster. Prometheus uses a lot of cycles. This is much lighter and you can actually send all your logs from your cluster using this.
This looks nice but a bit of a confusing nightmare to setup. I couldn't get syslog to work the way you outlined, I decided to use rsyslog to a local target in promtail but for some reason it get's angry if there are two local job names. Also the plugin for loki causes the docker container to hang if you attempt to restart it. Assuming I got all this running, I have no idea how to add sensors from remote servers. There must be a simpler way :/. Thanks for the effort though!
Thank you. This should work. Be sure you don't have scrape_configs: listed twice! Only once! I should probably add a note to the docs. I did this so you could comment one out and uncomment another but if you uncomment both you end up with a bad config.
@@TechnoTim Thanks! I got it working. I had tried only using scrape_configs just once but apparently it was picky about the syntax (I may have not tabbed over correctly or something). Now, please make a guide on how to add load/temps/Ethernet traffic from remote hosts. :)
Hey Tim, Love the video great job, How would this apply to the Raspberry Pi/Orange Pi/Rock Pi? Thanks for your hard work. Can it be installed on RPi 4 or the others I mentioned above?
hey Tim, can you make a tutorial on grafana for plex only within docker, saw some other vids and it is looking very cool to monitor plex with it. keep up the good work
Hi friends, Note : logs are from ubuntu server.... I'm looking for a log retention for 3 months in grafana loki .... How can we extend the retention period from the default 30 days to 90 days ??
I got this working well for standard logs . I'm curious if I can send other logs, like from ansible pull or from application that I write, to promtail as well. Google wasn't useful for answering this question, so maybe I'll hit up reddit and Grafana forums.
Hey Tim, great tutorial I had a bit of difficulty to set it up on my synology NAS, case, je deamon.json is not located in /etc/docker... it's in /var/packages/Docker/etc wich is a siimlink to /volume1/@appconf/Docker and second diff it's not named daemon.json but dockerd.json... this may help people using their Synology NAS to host a few apps ;)
Hi Tim thanks for all the good stuff you create! I really would like to log actions on my kids' windows 10 computers (they're 8 yo). Just "items" like which program has been started and on google & youtube what was being queried/returned/displayed... Do you have an idea how to achieve that?
Hey Tim - great information in your videos! Through lots of tinkering, I've managed to get k3s, cert-manager, rancher, traefik with tls certs up and running under Proxmox (I backed up my whole server, reformatted with Proxmox, created a VM and restored the server which runs 35+ containers in docker for my homelab). I want to get Grafana Loki but also want the prometheus and alerting too from your monitoring video. It looks like installing monitoring via the marketplace gets charts etc but do you just add loki rather than the loki stack? Adding loki stack seems to add things but there were no charts by default installed. Again, thanks for your awesome work. Your homelab machinery is sweet!
Hi! Thank you! Nice stack! Yeah, if you just want loki and grafana use the lokie stack (I have the commands in my docs) but you can also tailor the helm command if you already have grafana installed. This is probably what you want so that you can use your existing install.
@@TechnoTim So I installed the Rancher Monitoring package (brought in prometheus and customized grafana), installed standalone grafana and added rancher monitoring prometheus (worked), then installed loki-stack with just loki (with persistent storage), Promtail, and prometheus (could probably use the rancher monitoring one but couldn't figure out how to configure Promtail to use it vs the one it links to) enabled and added loki as a datastore to standalone grafana. Worked! So I have alerts now going to Slack, loki collecting and filtering logs, and grafana to view either prometheus or loki logs. Now just need to add in my Unifi data source and teslamate datastore once those containers are moved from docker-based system to k3s. Now back to the day job...
Your documentation (as far as copy & pasting goes) does not work anymore. Docker containers will not be able to find directories, or run without root, and will be stuck in a restart loop.
Hey Tim, great tutorial, I had decided on Loki already. Still, I have an issue with how to set up log retention using my Digitalocean space as external storage support, so I'm wondering if you got anything to share on that..?
Hi, I am setting up Grafana, Loki, and Promtail for an upcoming project, and I am using syslog-ng to receive logs from external devices. Can you create a video tutorial on using syslog-ng with Grafana Loki?
OK, nerd talk: What's your favorite logging system? (would this ever come up in a normal conversation???)
LibreNMS
For prod systems I really love Splunk
I've tried graylog, elk, datadog, cloud watch and a few others. Most are overkill, some are crazy expensive and none are perfect (or even great) Loki was on the 'check out at some point' list
ELK (elasticsearch, logstash, kibana)
@@VoislavVasiljevski ELK is definitely on the "one of the best" list. It's only down side is, it's resource intensive.
These guides are insane. No one goes to the detail that you do. You explain why and how commands and config files work rather that just reading them. Love your channel!
"Make sure you're in a directory... I dont know where else you'd be..." Made me laugh so hard xD
haha! I was going to re-record that part but I was like "just roll with it"
@@TechnoTim best decision
Root?
Great tutorial! One thing to note if you want to log specific docker containers you don't need to install promtail or change the deamon file. Just need the docker plugin for Loki and extra configuration in docker-compose for your specific containers that should use dedicated Loki logging driver.
Hello, this sound interesting can you give an example or link ? Thanks
Yes please, that will help a ton!
I've watched so many deployment videos trying to get a better all around understanding on all the NMS out there, what they can do, how they operate under the hood, etc. This by far is the absolute best I have seen and definitely earned you a sub. Most deployment videos tend to be quite dry, very un-explainative, and usually feel like a 'just do this real quick and it works' video. Thank you!!!
Been using Loki for over 2 years for work and play. Even out performed some enterprise level logging we tried too!
Nice! Thanks for sharing!
Thanks! This was informative! It's worth mentioning that Promtail is not required if you are setting Loki as the Docker daemon default logging driver
Please make a video for Tempo as well!
Then we can see how you monitor logs, traces and metrics using grafana and setting alerts!
That would be cool!
Tempo Maintainer here and YES! Would love to see that!
IDK may be I am wrong fix me if so. The man talks as if he is talking inside my brain. Awesome job
🤯
Hi Tim, you look like the kind of guy to keep (their system) up to date, but for those that may not know, there was a high-severity, zero-day vulnerability for Grafana a few days ago that enabled remote access to local files. Anybody that could access the site could access any file on the system, like for instance /etc/passwd. There are proof-of-concepts publicly available so it takes hardly any skill for script kiddies to start scanning.
Grafana released a fix right away. If you have not already, install the latest versions / patches!
+1 I've noticed this as well, but by using the "latest" tag the fixed version should be pulled next time you up the containers with the "--build" argument. Just want to add a small note for others as well, that using "latest" is not a best practice, and you should specify the version you want to use (especially in production), else you could end up pulling a vulnerable version without even realizing.
Thanks man! This is just so much easier and less troublesome then configuring a proper ELK stack.
Glad it helped!
Excellent! I am a long time user of Grafana and do a lot with it, but now the job is to manage the logs: here we are! Loki is the tool we want to deploy. Thanks a lot for your video, brillant, will be very helpful!
We went ahead and added Grafana and Loki to our TrueNAS SCALE Apps as well :)
Took some work, but well worth it ^^
5 min in and I can already tell your my new favorite tech guide guy. The detail is really welcome!
Before watching this video I was thinking to myself I wish Tim had a grafana tutorial.
Now, because of you, I want it ! Thanks for the great work.
Yo bro, I like your video and the way explained every single bit and steps are just beyond awesome. Thanks for this quality content. God bless you my friend.
GREAT VIDEO, got me through Loki and Syslog, thank you Tim
Just found your channel. I freaking LOVE these deep dives. Thank you so much for your hard work and insights!
Thank you and welcome!
I was waiting for this video. Very well explained as always, thanks Tim !
To take a quick glance at my docker logs, i like to use Dozzle, a very small and straight to the point tool, but it does the job
Thank you! Glad you liked it!
This was a lengthy but worth every second. Managed to get this up and running and Im happy but I would love a guide on getting syslog integrated
Nice work! Noted!
This is great and timely! Awesome vid! You make logging look fun! Gonna try it out right now!
Thank you! Let us know how it goes!
thank you for validating my use of nano. we are nano brothers, brother.
Remap Caps Lock to Ctrl if your control key is broken! Easier to reach, I do this by default. Great tutorial.
Thank you for the demo. I really appreciate it. I am in the process of setting up a syslog server.
Thank you for your great work, i think i have nearly a copy of your homelab in my home
Fantastic tutorial... everything explained really well, and worked perfectly.. great way to get up and running with Loki / Promtail / Grafana quickly!!
Glad it helped!
You know it's like really simple to develop plugins for Grafana? In my recent job we had to develop some very custom dashboards on the data we were collecting and it turns out Grafana has this whole eco-system to develop not only panel plugins, or data source plugins, but even app plugins, which integrate directly into the Grafana UI. It's really nice, since you get all user management and auto-reloading of data mechanisms for free :) And when I say easy, I mean really hard if you don't know it's basically React (and I didn't know React). But once you figure it out, it's easy.
It was an interesting video though, I had been wondering about this logging stack for a while and if I should chase it. The thing is, Kibana is just too powerful. Like even having unstructured data and being able to structure it on the fly is just everything.
Awesome tutorial Tim, as usual you nailed thank you for your hard work.
Thank you for the video. Helped a lot!
Thanks for the demo and info, have a great day
Thank you so much for the knowledgeable session
Thanks for this tuto. :) I get a lot of value from it :D
Thank you for your video. I enjoyed it very much and I know what I will do when I have some more free time around christmas this year.
Thank you! Me too!
Thanx a lot. Something that would be cool is to have a guide howto setup loki,mimir,tempo with grafana and prometheus in k8. Thanks!
Loki is great, very versatile. Be warned tho if you have limited storage space the loki database can grow in size quick!
Edit: loki doesn't trim old logs by default.. I only keep logs up to two weeks old. Huge data saver!
Good tip!
What config items do you need to set to change the default storage locations? I'm looking at their config reference and having trouble making sense of it
This is the first I though when Tim was explaining the setup.
Messing with influxdb but will check out Loki next. Wondering how Loki performs with TBs of logs without switching to cloud storage. Thanks for the video!
this tutorial was awesome, appreciate you!
New monitoring:
error and alert monitoring: CheckMK
performance monitoring: Prometheus + Grafana
log monitoring: Loki + Grafana
status monitoring: uptime kuma
Only need a trace management solution and you are all set up
Starting to get into k8s but wouldn't your alerting and status all be in Grafana?
@@MrNecrotik Yes its inside K8S. I think i will use two different grafana instances
Great presentation of some solid content! Thanks for sharing!
Thank you!
Gratefull i found this channel, thanks sir. Greeting from indonesia
You can't start logging this professional now dude, I stayed hidden so far from you but now it's impossible 🤣
You have so many docker tutorials and you're actuality running them in your house that... I have to...
I hereby declare you the docker King of RUclips!
Thanks 😅. I did get a little enterprise on this one, did I? 😆
@@TechnoTim This is what I want in my feed, some good knowledge instead of that Tiktok crap. 😉
The docker loki plugin had a serious problem, so it was not an option for production use. I don´ t know if this issue has been solved. The last time I was reading through the related issues the developers said, that they might not be able to provide a solution anytime soon. Let me describe: If your container host has high IO load and/or the loki server is not reachable for some reason the whole docker daemon hang up, because it wasn´t able to write the logs. The worst possible situation is when shutting down multiple containers. It wasn´ t possible to define some timeout. It was required to kill the daemon process and remove the container files (/var/lib/docker/containers) the daemon normally manages.
I never used the plugin again. I´m happy with configuring the log property of a container and have promtail to scrape this. The result is the same, but without the possibility of a blocked daemon.
Thanks for sharing your expertise and experience!
Is there a GitHub repository showing the various configuration files? That would be helpful.
Pfff ...this is great!! 😀
Thx man! Will definitely have a play with this! ✌️
Hope you enjoy it!
You are my inspiration!! Great job!!
i usually do Elasticsearch, i know its heavy in use and maintenance but also plugs into other things like my wiki so its great. Loki does look promising tho.
you can use ./bla (relative path) for binding volume
Thanks!
I love grep, awk, wc, uniq and sort commands :)
Awesome video, Tim! Could you share your dashboard config from 0:47? It looks like exactly what I need.
this video is great help
for the syslog, see if you can point the logs towards a dummy ip address. this way if someone gets into you system, they won't be able to find and mess with the logging server
Great explanation, thanks a lot.
Thanks for the overview! Just etc != etsy :D
Simply amazing
Can this be used in a closed source commercial product? The AGPL license is concerning. Even though no changes are made to the source code, and it would only be used for internal purposes, section 13 of the license is concerning. The software is a web application, so it would be accessible over a network, and while logs would obviously not be shown to end users, and technically aren't even necessary for the application to work, they are necessary for development and debugging.. Can't figure out whether it can be used in my company or not
Very Nicely Explained, keep it up.
Glad you liked it
Thanks for these excellent walk throughs. It's not easy to cover this level of stuff and still be interesting to watch.
Tried Loki, because it's easy to correlate it with Jaeger so you could check out traces based on trace ids found in logs. But to have advanced features on your logs, there's nothing else like elk+kibana. It only depends on what your needs are. Cheers and thumbs up for your videos ;) keep up the good work!
Good call! Thank you!
Thanks, great explanation indeed
Hi! Before all, amazing video!!
But, I'm having an issue when I try to do the first query, I see "No logs volume available". I already checked /ready and /metrics and looks good. Do you know which can be the problem?
Thanks a lot
Used graylog for a while, hated it. This looks much nicer, going to give it a whirl. Currently just aggregating into a rsyslog server with some scripts to compress and logrotate.
Need a tutorial on how to use Grafana Agent with the Grafana Loki
Hey Tim, great content as per usual!! I just saw your video and been struggling to set up logging from a firewall with this especially since promtail will be deprecated next year and they are switching to alloy. I wanted to know what are you using today in 2024 and if your still use this setup, have you migrated to alloy instead ?
I would like to reach a position where my ctrl and enter breaks. How can I do it?
very nice video, well done, thanks.
luvvvvv your channell
I swear software is annoying. If you look at the official docs to install this thing using docker-compose there's no mention of most of what Tim talks about. "Creake a loki folder and run this wget. Done." And if you look at the yaml file from the repo it's completely different than Tim's. If software developers knew how to communicate they'd be dangerous.
It’s because of the age of the video software has updates things change
excellent, man! We are evaluating right now a custom logging solution as the ones offered by major cloud providers are quite expensive... alternatives would have been an ELK stack, or something preconfigured as graylog... what do you think? Thanks
really depends on your infra! This is great for cloud, containers, kuerbernetes, and even traditional syslog. If you are already sing grafana that's a plus too!
Great video, I have a question about the promtail adding docker section. when you set up the docker loki driver, the daemon config was sending logs directly to loki so I am not sure what the promtail configuration actually did in this setup. Additionally, the promtail config was set to push from /var/lib/containers.... but this would have ben for the folder within the container of promtail only and not host. Have I missunderstood something?
You are correct, I believe the loki driver method is completely different form the promtail one with the docker pipeline stage
See the other comment I just posted about this for more details :)
really nice content dude!
1. Is Loki-Promtail stack suitable for aggregating and shipping logs that are generated at microsecond level?.
2. When logs are available in multiple files, promtail ships the logs in round robin fashion, spoiling the order of the logs. (Let's say logs generated through rolling file appender fashion).
Any comments will be helpful.
Great presentation! , thanks you
Glad you liked it!
Great video! I installed grafana, prometheus, loki and promtail on my Proxmox host and I am really liking it. One question: is there an easy way to get promtail to get logs from my Proxmox LXC containers and VMs? Or do I need to install promtail into each LXC/VM in order to get the logs into loki?
Hello, I have LXC containers (15) with dockers running inside, have you found a way to monitor them without installing the agent on all of them?
Awesome video @TechnoTim . Around the 15:24 mark, he was talking about how you would usually check Docker logs then scrolled down his container names, how did he do that? I'm assuming it is a particular shell, maybe? Anyone knows?
I am using zsh with oh-my-zsh and the docker plugin enabled. Search my website for zsh. I have examples.
very nice thanks for this
Thanks 😎
I seem to be missing something with the syslog portion. I set it up with the listening ports. I then went into one of my network devices and pointed it to loki on port 1514. Now what? I don't see anything in grafana indicating that any syslogs are coming in. I must be missing something really basic.
I used Rancher Monitoring from your previous tutorial with Grafana. I had to remove it since it uses a lot of resources.
Yeah, that installs prometheus, grafana, alert manager, and everything to log and alert for an entire cluster. Prometheus uses a lot of cycles. This is much lighter and you can actually send all your logs from your cluster using this.
This looks nice but a bit of a confusing nightmare to setup. I couldn't get syslog to work the way you outlined, I decided to use rsyslog to a local target in promtail but for some reason it get's angry if there are two local job names. Also the plugin for loki causes the docker container to hang if you attempt to restart it. Assuming I got all this running, I have no idea how to add sensors from remote servers. There must be a simpler way :/. Thanks for the effort though!
Thank you. This should work. Be sure you don't have scrape_configs: listed twice! Only once! I should probably add a note to the docs. I did this so you could comment one out and uncomment another but if you uncomment both you end up with a bad config.
@@TechnoTim Thanks! I got it working. I had tried only using scrape_configs just once but apparently it was picky about the syntax (I may have not tabbed over correctly or something). Now, please make a guide on how to add load/temps/Ethernet traffic from remote hosts. :)
Great tutorial!!! Is is difficult to get logs out of loki without Granfana Dashboard.
Hey Tim, Love the video great job, How would this apply to the Raspberry Pi/Orange Pi/Rock Pi? Thanks for your hard work. Can it be installed on RPi 4 or the others I mentioned above?
Thanks!
Wow! Thank you!
A new video, I love it // Vermium
Good to see you! Hope you're well!
@@TechnoTim I am! I hope you're well too!
hey Tim,
can you make a tutorial on grafana for plex only within docker, saw some other vids and it is looking very cool to monitor plex with it.
keep up the good work
The syslog configuration isn't working for me and since you didn't show it working I assume it didn't work for you either.
Hi friends,
Note : logs are from ubuntu server....
I'm looking for a log retention for 3 months in grafana loki .... How can we extend the retention period from the default 30 days to 90 days ??
Is there a video on how to set up the dashboard?
I got this working well for standard logs . I'm curious if I can send other logs, like from ansible pull or from application that I write, to promtail as well.
Google wasn't useful for answering this question, so maybe I'll hit up reddit and Grafana forums.
Hey Tim, great tutorial I had a bit of difficulty to set it up on my synology NAS, case, je deamon.json is not located in /etc/docker...
it's in /var/packages/Docker/etc wich is a siimlink to /volume1/@appconf/Docker
and second diff it's not named daemon.json but dockerd.json...
this may help people using their Synology NAS to host a few apps ;)
Great find!
Great video Tim as always! How do you add remote docker hosts on the promtail/loki configuration?
The same way but then point them to the remote server with promtail to ingest!
Great thumbnail! 😁
Haha! Thanks! I figured I would get creative on this one!
Hi Tim
thanks for all the good stuff you create!
I really would like to log actions on my kids' windows 10 computers (they're 8 yo).
Just "items" like which program has been started and on google & youtube what was being queried/returned/displayed...
Do you have an idea how to achieve that?
Yes I want to see how to push pfsense logs and I want to see what a logs dashboard would look like
Hey Tim - great information in your videos! Through lots of tinkering, I've managed to get k3s, cert-manager, rancher, traefik with tls certs up and running under Proxmox (I backed up my whole server, reformatted with Proxmox, created a VM and restored the server which runs 35+ containers in docker for my homelab). I want to get Grafana Loki but also want the prometheus and alerting too from your monitoring video. It looks like installing monitoring via the marketplace gets charts etc but do you just add loki rather than the loki stack? Adding loki stack seems to add things but there were no charts by default installed. Again, thanks for your awesome work. Your homelab machinery is sweet!
Hi! Thank you! Nice stack! Yeah, if you just want loki and grafana use the lokie stack (I have the commands in my docs) but you can also tailor the helm command if you already have grafana installed. This is probably what you want so that you can use your existing install.
@@TechnoTim So I installed the Rancher Monitoring package (brought in prometheus and customized grafana), installed standalone grafana and added rancher monitoring prometheus (worked), then installed loki-stack with just loki (with persistent storage), Promtail, and prometheus (could probably use the rancher monitoring one but couldn't figure out how to configure Promtail to use it vs the one it links to) enabled and added loki as a datastore to standalone grafana. Worked! So I have alerts now going to Slack, loki collecting and filtering logs, and grafana to view either prometheus or loki logs. Now just need to add in my Unifi data source and teslamate datastore once those containers are moved from docker-based system to k3s. Now back to the day job...
Your documentation (as far as copy & pasting goes) does not work anymore. Docker containers will not be able to find directories, or run without root, and will be stuck in a restart loop.
Hey Tim, great tutorial, I had decided on Loki already. Still, I have an issue with how to set up log retention using my Digitalocean space as external storage support, so I'm wondering if you got anything to share on that..?
Hi, I am setting up Grafana, Loki, and Promtail for an upcoming project, and I am using syslog-ng to receive logs from external devices. Can you create a video tutorial on using syslog-ng with Grafana Loki?
You have a mistake in the Docs it must be "sudo nano /etc/docker/daemon.json" not "sudo nano /etc/daemon.json"
Thank you! updated! fix rolling out now!
Hi Tim could I please request a Telegraf, Influxdb, Grafana video. It would be great to see a proxmox dashboard using the TIG stack. Thanks bro