Setup a Logstash server on Ubuntu

-
Pretty self explanatory and mainly for my own benefit, but easier to follow than the Elastic documentation.
# This is needed because the Azure Ubuntu build doesn't include the machine name in its hosts file
# This causes a delay every time you run sudo as it can't resolve the host name
# Once you're in the file, add the machine name to the end of the line "127.0.0.1 localhost"
$ sudo nano /etc/hosts
# Add the Elastic repository
$ wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
$ echo "deb https://artifacts.elastic.co/packages/6.x/apt stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-6.x.list
# Update package list to include Elastic packages
$ sudo apt-get update
# Install apt-transport-https. Likely already installed so just for safety really
$ sudo apt-get install apt-transport-https
#Install Java
$ sudo apt-get install default-jre
#Install logstash
$ sudo apt-get install logstash
# Update packages and install upgrades one more time for good luck
$ sudo apt-get update && apt-get upgrade
# Test Logstash
# See section below
$ sudo -Hu logstash /usr/share/logstash/bin/logstash -e 'input { stdin { } } output { stdout {} }'
# Start Logstash service
$ sudo systemctl start logstash.service
# Check it's running, albeit with errors
$ service logstash status
#Stop Logstash service and clear the log
$ sudo systemctl stop logstash.service
$ sudo rm /var/log/logstash/logstash-plain.log
#Copy config files from source control to your home folder on the logstash server using WinSCP as per section below on config files
#Once that's done proceed as follows with your username
$ sudo mv /home/<username>/pipelines.yml /etc/logstash/pipelines.yml
$ sudo mv /home/<username>/logstash.yml /etc/logstash/logstash.yml
$ sudo mv /home/<username>/app_logs.conf /etc/logstash/conf.d/app_logs.conf
# Start Logstash service
$ sudo systemctl start logstash.service
# Enable Logstash service to run at startup
$ sudo systemctl enable logstash.service
# Check it's running
# You want to see:
# Restored connection to ElasticSearch
# Pipelines running
# Starting server on port: <portnumber from pipelines.yml>
# Successfully started Logstash API endpoint
$ service logstash status
# Now start sending it some logs!
view raw logstashinstall hosted with ❤ by GitHub

Comments

Post a Comment

Popular posts from this blog

DFS "Waiting for Initial Replication"

-
Taken directly from  Technet Forum  post by  scorprio_milo . Pop along and give them an up vote! You may encounter the error message "waiting for initial replication" when no primary member is currently specified on the DFS Replication. This DFS member is waiting for initial replication for replicated share folder Public and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory. After the member detects that it is part of replication group, the member will begin initial replication.  Besides, there is also possiblity that DFS servers cannot contact domain controller which could result in the issue. 1. Please first verify that all the target folder of Public folder is enabled.   2. Please use Dfsradmin to set the primary member in the situation where there is an existing replication group that is waiting...
Read more

Avoid Microsoft Intune if you use G-Suite and Android

-
Like me, you might have considered Intune to be your one stop MDM solution if you're an Office/Microsoft 365 user. On the whole it is pretty good, but it's got one massive failing: It doesn't support Google accounts on Android Work Profiles. You might think that if you're a Microsoft shop it's not a big deal, but there two major reasons why you might want to use Google alongside Azure Active Directory: SSO. Many companies charge extra for SSO with Azure but include it for free with Google, e.g. Slack and Atlassian. Chrome. Let's face it, everyone uses Chrome rather than Edge so signing in with a Google account to sync your favourites is pretty handy. Managing this setup in an organisation is pretty easy. Sign up for G-Suite account, sync all your users from Azure AD, configure G-Suite to use AAD for authentication and you're done. Enterprise managed Google accounts for everyone at zero cost if you don't actually need G-Suite. Given the abo...
Read more

Setting Wallpaper for a Remote Desktop Session

-
Ah, the fun I had trawling around trying to find out how to set the wallpaper on a remote desktop session! The (seemingly) most obvious answer was changing the Wallpaper setting under Desktop in a GPO, but no. That setting explicitly states that it doesn't apply to RDP sessions, so back to the registry we go... I'm presuming here that we want these settings to apply to all the computers within a specific OU rather than to individual users. Create a new GPO "Wallpaper" Navigate to Computer Config/Policies/Admin Templates/System/Group Policy Set "Configure user Group Policy loopback processing mode" to Enabled with Mode as "Merge" Navigate to Computer Config/Policies/Admin Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment Set "Always show desktop on connection" to Enabled Set "Enforce Removal of Remote Desktop Wallpaper" to Disabled Navigate to Computer Con...
Read more