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!!!
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.
Fantastic tutorial... everything explained really well, and worked perfectly.. great way to get up and running with Loki / Promtail / Grafana quickly!!
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!
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.
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
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.
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.
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
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 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.
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
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.
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
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.
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?
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 TH-cam!
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 :)
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 ?
Hi , I tried to extract logs from mssql server using promtail , loki grafana I window environment, logs are coming to grafana dashboard. Problem here is in logs words are displaying as I n s t a n c e instead of instance. Can you please help with solution to resolve my issue.
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.
Good day i got this error when install plugin docker plugin enable loki Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/etc/resolv.conf" to rootfs at "/etc/resolv.conf": stat /etc/resolv.conf: no such file or directory: unknown ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 Dec 26 16:15 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
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?
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.
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. Thanks for putting this info out. I will use it to monitor my home network. QQ on syslog, once I place the configuration in the yaml file, I dnt need to use something like rsyslog on a server to listen to the syslog and forward it to promtail? I can send the my syslog directly to promtail container on port 1514?
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?
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 ??
Hi , may I know how to add the prometheus , snmp exporter also include in the docker? My purpose is monitor linux system, windows system , and network deivce e.g Cisco switch , FortiGate firewall . Thank you
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!
Stupid question, what do you use for SIEM solution in this setup, LOKI is not one or do they plan on it as per github. What would you forward logs to? Graylog or ELK?
Unfortunately, I found that the syslog functions do not work with my firewall (SonicWALL) and promtail. Looking at some dashboards on Grafana related to SonicWALL it says something about setting up rsyslog in front of promtail to get it to work.
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?
I also used 24:24 and its really awesome, but now there's issue i could not fix, in kubernetes 1.22.x chart is deprecated and solution is to update clusterrole to /v1 from /v1beta1 but no idea in helm how to?
Hey, Thanks for providing docker-compose grafana loki setup. Could you please kubernats (using kind) grafana loki yml if possible(for capturing the ISTIO logs)
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!!!
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.
Fantastic tutorial... everything explained really well, and worked perfectly.. great way to get up and running with Loki / Promtail / Grafana quickly!!
Glad it helped!
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!
IDK may be I am wrong fix me if so. The man talks as if he is talking inside my brain. Awesome job
🤯
Thanks man! This is just so much easier and less troublesome then configuring a proper ELK stack.
Glad it helped!
Now, because of you, I want it ! Thanks for the great work.
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
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!
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!
5 min in and I can already tell your my new favorite tech guide guy. The detail is really welcome!
thank you for validating my use of nano. we are nano brothers, brother.
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.
We went ahead and added Grafana and Loki to our TrueNAS SCALE Apps as well :)
Took some work, but well worth it ^^
GREAT VIDEO, got me through Loki and Syslog, thank you Tim
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!
Thanks for this tuto. :) I get a lot of value from it :D
Thanks!
Wow! Thank you!
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!
Awesome tutorial Tim, as usual you nailed thank you for your hard work.
Before watching this video I was thinking to myself I wish Tim had a grafana tutorial.
Thanks for the demo and info, have a great day
Thank you for the video. Helped a lot!
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!
Thank you for the demo. I really appreciate it. I am in the process of setting up a syslog server.
Thank you so much for the knowledgeable session
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
You are my inspiration!! Great job!!
Great presentation of some solid content! Thanks for sharing!
Thank you!
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!
this tutorial was awesome, appreciate you!
Remap Caps Lock to Ctrl if your control key is broken! Easier to reach, I do this by default. Great tutorial.
Thank you for your great work, i think i have nearly a copy of your homelab in my home
Gratefull i found this channel, thanks sir. Greeting from indonesia
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!
really nice content dude!
Awesome video, Tim! Could you share your dashboard config from 0:47? It looks like exactly what I need.
Thanks man you made my day :)
Very Nicely Explained, keep it up.
Glad you liked it
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.
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
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!
Hi , i would like to say thank you !
Thanks for these excellent walk throughs. It's not easy to cover this level of stuff and still be interesting to watch.
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.
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
Pfff ...this is great!! 😀
Thx man! Will definitely have a play with this! ✌️
Hope you enjoy it!
Awesome video!
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
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.
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.
Great explanation, thanks a lot.
you can use ./bla (relative path) for binding volume
Thanks!
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.
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.
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 TH-cam!
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. 😉
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 :)
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!
I would like to reach a position where my ctrl and enter breaks. How can I do it?
I love grep, awk, wc, uniq and sort commands :)
Thanks, great explanation indeed
very nice video, well done, thanks.
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
Hi, is this fixed?
I'm also facing similar issue
Thanks,
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.
Simply amazing
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 ?
Hi , I tried to extract logs from mssql server using promtail , loki grafana I window environment, logs are coming to grafana dashboard. Problem here is in logs words are displaying as I n s t a n c e instead of instance. Can you please help with solution to resolve my issue.
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.
Good day
i got this error when install plugin
docker plugin enable loki
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/etc/resolv.conf" to rootfs at "/etc/resolv.conf": stat /etc/resolv.conf: no such file or directory: unknown
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Dec 26 16:15 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
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?
Great thumbnail! 😁
Haha! Thanks! I figured I would get creative on this one!
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.
Great presentation! , thanks you
Glad you liked it!
Can this be done in a VM? I really don't have the time to learn about docker, containers. Thanks.
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.
Thanks for the overview! Just etc != etsy :D
Great video. Thanks for putting this info out. I will use it to monitor my home network. QQ on syslog, once I place the configuration in the yaml file, I dnt need to use something like rsyslog on a server to listen to the syslog and forward it to promtail? I can send the my syslog directly to promtail container on port 1514?
A new video, I love it // Vermium
Good to see you! Hope you're well!
@@TechnoTim I am! I hope you're well too!
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?
very nice thanks for this
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?
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 ??
Hi , may I know how to add the prometheus , snmp exporter also include in the docker?
My purpose is monitor linux system, windows system , and network deivce e.g Cisco switch , FortiGate firewall . Thank you
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!
this video is great help
Stupid question, what do you use for SIEM solution in this setup, LOKI is not one or do they plan on it as per github. What would you forward logs to? Graylog or ELK?
Unfortunately, I found that the syslog functions do not work with my firewall (SonicWALL) and promtail. Looking at some dashboards on Grafana related to SonicWALL it says something about setting up rsyslog in front of promtail to get it to work.
Need a tutorial on how to use Grafana Agent with the Grafana Loki
Liked and subscribed. Thanks for sharing.
Thanks for the sub!
And for the like!
and for the comment! 🚀
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?
let me ask 1 question Loki is possible to connect with old container logs after using docker plugin
I also used 24:24 and its really awesome, but now there's issue i could not fix, in kubernetes 1.22.x chart is deprecated and solution is to update clusterrole to /v1 from /v1beta1 but no idea in helm how to?
We'll have to wait for grafana to update this. This is just a deprecation warning, it still works.
Hey, Thanks for providing docker-compose grafana loki setup. Could you please kubernats (using kind) grafana loki yml if possible(for capturing the ISTIO logs)