On this channel you will find tutorials, tips, tricks, reviews and more of popular open source products. Focusing more on the network management side of things.
I installed everything as per the instructions, but I am still getting "502 Bad Gagway | nginx/1.18.0 (Ubuntu)" in the browser. I am not sure what is the issue. I am using VirtualBox with Ubuntu Server 22.04.4 as OS, and PHP version is 8.1.2.
I just built my Graylog server to collect and analyze my OPNsense logs (filterlog for now) and I have literally zero knowledge on how use that tool. I managed to set up sending logs to Greylog and now it's time to make the next steps. Your channel is exactly what I was looking for :)
Thanks for your video. As I never wrote anything in python, I cannot guess what is written on the right part of your script... so frustrating !!! I would libe to see a working exemple before modifying it or create my own. Regards.
Hi, thanks for all these videos on graylog. You should use "systemctl edit graylog-server" to override the unit. This will create a file (/etc/systemd/system/graylog-server.service.d/local.conf) with just the additions to graylog-server.service. That way you don't touch the original file and your changes will survive on upgrading (this is systemd standard feature).
Very nice series of videos! Could you elaborate a bit more in one of the next videos around the Authentication story you mentioned at the end of this one for all the streams you have? I am missing a couple of bits left and right there...
Thanks for the good video! I would like to know whether the communication between log sources (senders) and the Graylog server secured by TLS encryption?
We have installed distributed poller watching your video and we are running dispatcher services but we have one issue graph are not generating.Please help
thank for the graylog video :) I am very new with graylog and start to build demo graylog's architecture to save the log data. I would like to ask about is it possible to set index name as daily format? (ex. graylog_20240215, graylog_20240216) The default setting produces index name like 'graylog_0' ...
What issue are you trying to solve? If you want ALL logs from a certain time period I would be using the date selectors when searching. I don't think you can change that format,
@fordayinlife Thank you for the quick response! There are no issues, but I would like to know whether I can handle Graylog's index name as I want. Here is my plan for the graylog system: 1) generating graylogs' index and setting its name as daily format (ex. graylog_20240216...) 2) Making a snapshot for the index and saving it to AWS S3 by opensearch dashboard 3) Delete the old index with certain rules (ex., deleting the old index after 6 months). 4) Restoring the deleted index from AWS S3 by opensearch dashboard when I want. 5) For this purpose, I would like to set the graylog's name as a daily format to pick up and restore it by using file name.
This installment in your Graylog series was worth the wait. I think I finally “get” grok patterns now. I would love to see how pipelines can parse JSON into key value pairs (idea for future video). I know I can do it with string matching and grok patterns but that seems fragile and inefficient.
hey. I followed step by step guide and it's end-up showing bad-gateway error while tried to check for pre-install check. can anyone give me the solution for this error?
Very nice explanation for pipeline. But I have one question: I've did it for my source field with the input is localhost to be changed to a specific IP of the server. But the problem is any servers coming in graylog with the source named localhost were changed to this IP (as the pipeline rule I set). So how do I distinguish different IPs from different servers which coming into graylog with the same name localhost? Tks!
@@fordayinlife it's weird for my case, I've never seen any messages if I filter Gl2_remote_ip key, so I always have to use source or SourceModuleName or ServiceName to be able to looking up for the messages.
