iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
Centralize Linux logs by running Elasticsearch and Kibana on one protected VPS, Logstash as the processing layer, and Filebeat on every server that produces logs. Filebeat sends events to Logstash, Logstash parses and enriches them, Elasticsearch stores and searches the resulting documents, and Kibana displays them in Discover and dashboards.
The reliable build order is Elasticsearch, Kibana, Logstash, then Filebeat (or Elastic Agent). Keep every Elastic Stack component on the same version line, expose only the Beats input to trusted senders, and verify ingestion in Elasticsearch before troubleshooting Kibana.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What the centralised logging architecture does
A central logging VPS gives you one search point for authentication records, system messages, web-server access logs, application errors and other text files that would otherwise be scattered across machines. The data path is deliberately split into collection, processing, storage and presentation so each part has a clear job.
| Component | Runs on | Responsibility |
|---|---|---|
| Filebeat | Each source Linux server | Reads configured files or modules, tracks its registry so lines are not repeatedly resent, and forwards events. |
| Logstash | Central VPS, or a separate host when processing is heavy | Receives Beats events, applies filters such as Grok, adds fields and routes documents to Elasticsearch. |
| Elasticsearch | Central VPS or managed cluster | Indexes, stores and searches the structured events. |
| Kibana | Central VPS or managed service | Provides Discover, visualisations, dashboards and administration for the indexed data. |
Elastic describes the Logstash event processing pipeline as “inputs → filters → outputs.” Your input is normally the Beats protocol on TCP port 5044, the filter block turns unstructured lines into fields, and the Elasticsearch output writes those fields to an index.
#1 Best Overall
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
Choose where to run the stack
A single Linux VPS is appropriate for a small, low-volume installation when you size storage and memory for the retention period and event rate you actually have. There is no universal RAM or events-per-second figure: log formats, parsing rules, burstiness, replica settings and retention all change the requirement. Measure your workload and leave headroom rather than copying a generic benchmark.
| Decision factor | Self-managed VPS | Managed Elastic or cloud deployment |
|---|---|---|
| Monthly cost | VPS, storage, backups and bandwidth are billed separately; the total depends on the selected size and retention. | Provider pricing usually bundles infrastructure and service operations; calculate storage, ingest and retention charges from the current plan. |
| Operations | You patch packages, rotate certificates, tune JVM and Logstash settings, test backups and respond to incidents. | The provider handles more host maintenance and offers managed scaling, while you still manage data, users and pipeline configuration. |
| Scaling | Resize the VPS or add dedicated Logstash and Elasticsearch nodes as demand grows. | Scaling controls are easier to use, but service limits and topology are provider-specific. |
| Security responsibility | You control firewall rules, TLS, credentials, OS hardening and network placement. | The provider secures the service perimeter; you must still configure authentication, least privilege and safe shipper connectivity. |
| Retention control | Choose index lifecycle, deletion and backup policies directly. | Retention and snapshot features depend on the service edition and incur its storage costs. |
| Geographic placement | Place the VPS in a region close to the sources or users, subject to your host’s locations. | Select an available provider region and confirm cross-region transfer and residency terms. |
Elastic documents Elastic Cloud Hosted as an available managed path. Whichever model you choose, keep a written retention policy and decide where backups and certificates will live before sending production data.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Plan versions, network paths and retention first
Pin one compatible version line
Elastic requires the products in a deployment to use the same version. Pin the 9.x repository or package versions consistently on Elasticsearch, Kibana, Logstash and Filebeat (or Elastic Agent), and upgrade them as a coordinated change. Mixing major or minor lines can produce incompatible configuration, APIs or saved objects.
Define the allowed network flows
- Source servers need outbound TCP access to the Logstash Beats input, normally port 5044.
- The central VPS needs local access between Logstash and Elasticsearch, commonly through the Elasticsearch HTTP endpoint on localhost when both share a host.
- Administrators need controlled access to Kibana, normally through a private network or a reverse proxy with HTTPS and authentication.
- Do not expose Elasticsearch’s HTTP port or the Logstash monitoring endpoint to the public internet unless a specific, hardened design requires it.
Estimate storage from your own logs
Record the uncompressed daily volume from each source, the number of retained days, whether replicas are enabled, and the space used by parsed fields and metadata. Include filesystem headroom for merges, upgrades and bursts. If Logstash filters consume substantial CPU or memory, plan a separate Logstash host rather than forcing parsing and storage onto one small VPS.
Prepare and harden the Linux VPS
- Install a supported Debian/Ubuntu or RPM-based Linux release and apply current security updates.
- Set a stable hostname and UTC time synchronization. Consistent clocks make the
@timestampfield and incident timelines meaningful. - Create an administrative account with SSH keys, disable password SSH where your policy permits, and restrict SSH to trusted addresses.
- Configure the host firewall to allow established connections, administration from trusted networks, Kibana access for operators, and TCP 5044 only from the source servers that ship logs.
- Use the deployment’s authentication and TLS controls for Elasticsearch, Kibana and Beats. Store credentials and certificate files with restrictive permissions and rotate them according to your security policy.
Port 5044 is an example, not a requirement. You may choose another port, but the Logstash input, Filebeat output and firewall rule must match exactly.
Install Elasticsearch, Kibana and Logstash
Elastic publishes DEB, RPM, archive and Docker distributions. Package installation is the simplest fit for a conventional VPS because each component can run under its service manager.
Rank #2
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
Debian or Ubuntu
Import Elastic’s signing key, add the 9.x APT repository for your distribution, refresh package metadata, and install the packages. Use the repository instructions for the exact key and repository entry for your release; do not mix a repository from another major version.
sudo apt-get update
sudo apt-get install elasticsearch kibana logstashEnable and start services only after their configuration and credentials are ready. Installing Elasticsearch and Kibana first follows the supported dependency order; install Logstash next.
RPM-based systems
Import the Elastic signing key, create the matching 9.x YUM repository definition, refresh metadata and install the same three packages.
sudo yum install elasticsearch kibana logstashUse the package-provided systemd units. Archive and Docker deployments are valid alternatives when you already operate those delivery methods, but keep image or archive versions aligned with the Beats package.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Configure Elasticsearch
Edit /etc/elasticsearch/elasticsearch.yml with the node name, data and log paths appropriate for your disk layout. For a single-stack VPS, binding Elasticsearch to localhost keeps the HTTP API off the public interface while Logstash and Kibana use it locally. If another host must connect, bind only to a private interface and enforce TLS and authentication.
Start Elasticsearch, obtain or set the deployment’s administrator credentials and verify that its HTTP API responds over the configured TLS endpoint. Do not disable security merely to make a test request succeed.
Rank #3
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Configure Kibana
Edit /etc/kibana/kibana.yml to point Kibana at the Elasticsearch endpoint and supply the service credentials or enrollment settings generated by your Elastic deployment. Bind Kibana to localhost when a reverse proxy or VPN is in front of it; otherwise bind to a private address and protect it with HTTPS, authentication and an allow-list.
Build a Logstash pipeline
Place a pipeline file such as /etc/logstash/conf.d/linux-logs.conf. Start with an input, add only the filters you need, and finish with an Elasticsearch output. The following pattern accepts Filebeat events on port 5044, parses Apache-style access lines when the message matches that format, and writes daily indexes.
Free tools Windows power users keep installed
One-click scans. No signup required.
input {
beats {
port => 5044
}
}
filter {
if [log][file][path] =~ /access.log/ {
grok {
match => { "message" => "%{COMBINEDAPACHELOG}" }
}
date {
match => [ "timestamp", "dd/MMM/yyyy:HH:mm:ss Z" ]
target => "@timestamp"
}
}
}
output {
elasticsearch {
hosts => [ "https://localhost:9200" ]
index => "logstash-%{+YYYY.MM.dd}"
}
}Use the Elasticsearch URL, credentials and certificate settings required by your secured installation. If Elasticsearch is on another host or cluster, replace the localhost endpoint with that private cluster endpoint. The daily index expression is an example; choose a naming and lifecycle policy that matches your retention plan.
Test the pipeline before production traffic
- Validate the configuration with the package’s Logstash test option or a foreground start that reports configuration errors.
- Confirm that the Beats input binds to the intended interface and port.
- Send one known test line from a source host and watch the Logstash service log for connection or filter errors.
- Check the resulting document in Elasticsearch before creating Kibana views. This separates ingestion problems from visualisation problems.
Install and configure Filebeat on every source server
Install the Filebeat package from the same Elastic version line on each Linux server being monitored. Filebeat is designed to be lightweight and resource-friendly: it tails files, maintains a registry of read offsets and forwards events instead of performing heavy parsing locally.
Configure file inputs and the Logstash destination
Edit /etc/filebeat/filebeat.yml and list the actual paths to monitor. Send output to the central Logstash host rather than directly to Elasticsearch.
filebeat.inputs:
- type: filestream
id: linux-system-logs
enabled: true
paths:
- /var/log/*.log
- /var/log/**/*.log
output.logstash:
hosts: ["logstash.internal:5044"]Use a resolvable private hostname or address for your Logstash server, and configure the Beats TLS options with the CA and client settings required by your security design. Avoid broad recursive paths that capture Filebeat’s own output or high-volume data you did not intend to retain.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Entry-level NAS Home Storage: The UGREEN NAS DH4300 Plus is an entry-level 4-bay NAS that's ideal for home media and vast private storage you can access from anywhere and also supports Docker but not virtual machines. You can record, store, share happy moment with your families and friends, which is intuitive for users moving from cloud storage, or external drives to create your own private cloud, access files from any device.
- Smart Photo Backup & AI Album: Automatically back up photos and videos from your phone in real time and keep growing family memories organized with AI-powered photo albums. Semantic search, custom learning, and recognition of people, objects, pets, and similar photos help you quickly find the moments you want. Duplicate photo removal also helps keep your library organized—ideal for families and users with large photo collections.
- User-Friendly App & Easy Setup: Connect quickly via NFC, set up simply and share files fast on Windows, macOS, Android, iOS, web browsers, and smart TVs. You can access data remotely from any of your mixed devices. What's more, UGREEN NAS enclosure comes with beginner-friendly user manual and video instructions to ensure you can easily take full advantage of its features.
- More Cost-effective Storage Solution: Unlike cloud storage with recurring monthly fees, A UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $629.99 for a NAS, while for cloud storage, you need to pay $719.88 per year, $1,439.76 for 2 years, $2,159.64 for 3 years, $7,198.80 for 10 years. You will save $6,568.81 over 10 years with UGREEN NAS! *NAS cost based on DH4300 Plus + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Your Data, You Control：No third-party clouds, no hidden access, UGREEN NAS provides a more secure and private data storage solution. It stores data locally on your private hard drives and does automatic backups. Thus, you can keep full control over it. The advanced encryption is TRUSTe certified in the United States and is awarded the first (and only) ETSI EN 303 645 certification mark for NAS products by TÜV SÜD Group.
Enable modules for common services
When a supported module exists, it supplies tested input paths and field mappings for that service. For example, enable the system module for common Linux system and authentication logs, then inspect the module’s paths before starting it.
sudo filebeat modules enable system
sudo filebeat test config
sudo filebeat test outputEnable web-server or other service modules only when those services are present and their log locations match the module configuration. Module availability and field sets vary by Elastic version.
Start Filebeat safely
- Run the configuration and output tests and correct YAML indentation, certificate paths and DNS errors.
- Enable and start Filebeat with systemd.
- Generate a single test event on the source host, note its UTC time and hostname, and follow it through the pipeline.
- Keep the Filebeat registry intact during routine restarts; deleting it can cause old lines to be resent or create gaps in your audit trail.
Start services in dependency order
On the central VPS, start Elasticsearch first, then Kibana, then Logstash. Once the Beats input is listening, start Filebeat on source servers.
sudo systemctl enable --now elasticsearch
sudo systemctl enable --now kibana
sudo systemctl enable --now logstash
# Run on each source server
sudo systemctl enable --now filebeatUse systemctl status and the journal for each service when a unit fails. A service can be active while still unable to authenticate to its next hop, so complete the end-to-end test rather than relying only on process status.
Verify ingestion from disk to Kibana
Check Logstash and Elasticsearch first
Use an authenticated request to Elasticsearch’s search API or the daily index naming pattern to confirm that documents arrive. The exact URL scheme and CA option depend on your TLS configuration.
curl -u elastic https://localhost:9200/_cat/indices?v
curl -u elastic 'https://localhost:9200/logstash-*/_search?size=1&sort=@timestamp:desc'The first request lists indexes; the second retrieves a recent document. Supply the password interactively and the CA option required by your deployment. If you see no index, inspect the Filebeat connection, Logstash input and Logstash output in that order.
Best Value
- Value NAS with RAID for centralized storage and backup for all your devices. Check out the LS 700 for enhanced features, cloud capabilities, macOS 26, and up to 7x faster performance than the LS 200.
- Connect the LinkStation to your router and enjoy shared network storage for your devices. The NAS is compatible with Windows and macOS*, and Buffalo's US-based support is on-hand 24/7 for installation walkthroughs. *Only for macOS 15 (Sequoia) and earlier. For macOS 26, check out our LS 700 series.
- Subscription-Free Personal Cloud – Store, back up, and manage all your videos, music, and photos and access them anytime without paying any monthly fees.
- Storage Purpose-Built for Data Security – A NAS designed to keep your data safe, the LS200 features a closed system to reduce vulnerabilities from 3rd party apps and SSL encryption for secure file transfers.
- Back Up Multiple Computers & Devices – NAS Navigator management utility and PC backup software included. NAS Navigator 2 for macOS 15 and earlier. You can set up automated backups of data on your computers.
Create the Kibana data view
- Open Kibana through its protected URL and sign in with an account allowed to view the log indexes.
- Open the data-view management screen and choose Create data view (the label can vary slightly by Kibana release).
- Enter
logstash-*if the pipeline above writes daily Logstash indexes, or enter the actual index prefix produced by your output. - Select
@timestampas the time field. - Open Discover, set a time range that includes the test event, and filter by the source hostname or file path.
Elastic’s example daily index uses UTC for the date portion. Compare test-event timestamps in UTC when an event appears one day earlier or later than expected.
Trace one event through every hop
- Source file or syslog: confirm the test line is written and readable by the Filebeat service account.
- Filebeat registry: verify that the harvester has advanced its offset and that no permission or fingerprint warning is present.
- Logstash: check that the Beats connection is accepted and that Grok did not tag the event with a parse failure.
- Elasticsearch: confirm index creation and inspect the raw document, including
host.name,log.file.pathand@timestamp. - Kibana: refresh the data view fields and widen the time range if the document is indexed but not visible.
Make unstructured logs useful
Parsing is valuable only when it is tied to a known log format. Start with one service, preserve the original message field, and add a Grok pattern or dissect rule that extracts stable fields such as client address, request, status code, response size and user agent. Add conditional filters based on the source path or Filebeat module so an Apache pattern is never applied to kernel or authentication lines.
Use date parsing to place the event’s original timestamp in @timestamp. If a line has no reliable embedded time, retain Filebeat’s collection time and document that choice. Add tags or fields for environment, application and ownership so Kibana filters do not depend on fragile filename matching.
Operate the installation after the first successful event
Retention and index growth
Daily indexes make it easy to reason about age, but they do not automatically enforce retention. Define an index lifecycle or scheduled deletion policy that removes data only after the approved retention period, and test it on a non-production pattern. Monitor free disk space, shard counts and merge activity; a full data volume can stop indexing and make recovery harder.
Backups and recovery
Back up Elasticsearch snapshots to storage independent of the VPS. Backing up only the VPS disk is not a substitute for tested snapshots, and copying active data directories without the supported procedure can produce an unusable restore. Periodically restore a sample index and verify that Kibana data views and credentials can be recreated.
Recommended Free Tools
Updates and configuration changes
Keep package repositories pinned to the intended version line, read the upgrade notes, snapshot before upgrades and update components in a supported sequence. Validate Logstash configuration and Filebeat output after every change. Record pipeline files, Kibana saved objects, firewall rules and certificate renewal steps in version control or a restricted configuration archive.
Capacity signals
- Persistent Logstash queue growth or rising pipeline latency indicates that filters or outputs cannot keep up.
- High JVM pressure, long garbage-collection pauses or frequent Elasticsearch write rejections indicate storage or memory pressure.
- Filebeat backpressure and an expanding registry gap mean source events are waiting to be shipped.
- Disk usage rising faster than the retention plan requires shorter retention, more storage or a different index strategy.
Scale beyond one VPS
Move Logstash to its own host when parsing is resource-heavy or when its CPU spikes interfere with Elasticsearch. Move Elasticsearch data to dedicated or multiple nodes when storage, availability or ingest demand exceeds one VPS. Kibana can remain separate from the data nodes, and Filebeat can continue sending to a load-balanced or clustered Logstash endpoint. A managed deployment becomes attractive when you need easier horizontal scaling and less host maintenance, provided its pricing, regions and retention controls meet your requirements.
Troubleshoot common failures
| Symptom | Likely cause | Action |
|---|---|---|
| Filebeat reports connection refused or timeout | Firewall, wrong hostname, wrong port or Logstash is not listening. | Check DNS and routing from the source, confirm the Beats input port with ss -lnt, and allow only the source address in the VPS firewall. |
| Logstash starts then exits | Invalid pipeline syntax, unavailable plugin setting or certificate permission. | Run the configuration test, read the system journal, fix the reported line and verify that the service account can read referenced files. |
| Elasticsearch receives no documents | Output authentication/TLS failure, wrong endpoint or a filter routing event elsewhere. | Inspect Logstash output errors, test the Elasticsearch API from the VPS and search all expected index prefixes. |
| Documents exist but Discover is empty | Wrong data-view pattern, stale field list or a time range that excludes the event. | Match the actual index name, refresh fields, select @timestamp and widen the time range using the UTC event time. |
| Fields are missing or marked as parse failures | Grok pattern does not match that service’s format. | Inspect the original message, scope the filter by source path, and create a pattern for the exact format instead of broadening a working rule. |
| Events appear duplicated | Filebeat registry was removed or input paths overlap. | Restore the registry from the supported backup if possible, remove overlapping paths and deduplicate downstream only after preserving the originals. |
| Disk fills unexpectedly | Retention policy is absent, log volume increased or debug logging is enabled. | Measure index growth, enforce lifecycle deletion, reduce unnecessary collection and expand storage before Elasticsearch reaches its watermark. |
A disciplined installation therefore has a clear boundary: Filebeat collects, Logstash transforms, Elasticsearch indexes and Kibana presents. Keep the versions aligned, protect every network hop, verify a known event at each stage, and split processing or storage onto additional hosts when the measured workload outgrows a single VPS.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
