Search iThub

Search tools, categories and collections. Type at least two characters.

Explore all tools
↑ ↓ to explore resultsEnter to open · Esc to close

Log Management

Tools that collect, store, search and analyze logs from servers, containers and applications.

Choosing guide

9 results in Log Management

Active Pro listings from this category appear first. Your sort applies within Pro and Free results.

Advertisements
Advertisements
Focused collections

Shortlists for Log Management

Explore collections with tools relevant to this category, grouped by deployment, source model or workload.

Monitoring tools for MSPs →

2 matching tools from this category

Self-hosted monitoring tools →

3 matching tools from this category

How to choose log management tools

Log management tools collect log lines from servers, containers and applications, ship them to a central store, and let you search, filter and alert on them. They answer what happened and when during an incident, and they keep audit trails for the retention period you set. They overlap with observability suites but center on text events rather than metric dashboards, and they stop short of SIEM, which adds security correlation on top.

Read the guide

Who uses these tools

  • Sysadmins troubleshooting failing services on Linux hosts
  • SREs investigating incidents across container clusters
  • Developers tailing application output during debugging

Capabilities to compare

  • Agents and shippers for files, journald and containers
  • Query language and full-text versus label indexing
  • Retention tiers and object storage backends
  • Alerting rules on log patterns and rates
  • Multi-tenancy and per-team access control

Operating considerations

  • Ingest volume drives storage and SaaS cost
  • Retention requirements from audit and privacy rules
  • Masking secrets and personal data before shipping
  • Index strategy affects query speed and disk usage
  • Exporting archived logs if you change provider

Selection checklist

  1. Measure your daily log volume per source before comparing pricing or sizing storage for a self-hosted stack.
  2. Run the queries your team uses most during incidents and time them against a realistic data set.
  3. Confirm that the shipper supports every source you run, including containers, syslog and cloud service logs.
  4. Check how retention, deletion and access logging work so the store meets your compliance obligations.

What belongs in this category: Listed products ingest, store and query log data as their core function, whether as a local viewer, a self-hosted aggregator or a managed service, rather than treating logs as a side feature of monitoring.

Log Management on iThub in figures

iThub lists 9 tools in Log Management. 6 of 9 are open source, 6 of 9 can be self-hosted, 7 of 9 have a free, freemium or open-source pricing model and 9 of 9 offer an API.

Tools listed
9
Open source
6
Self-hostable
6
Free to start
7
With an API
9
Web app
6
Desktop app
4

Recently added: Vector, Datadog, Uptrace, New Relic

Typical use cases

  • Centralizing syslog and journald output from a fleet of servers
  • Tracing an error across several microservices during an incident
  • Keeping searchable audit logs for a fixed retention period
  • Streaming local log files into a browser view while debugging

Trade-offs to model

  • Label-based indexing keeps storage cheap but makes free-text searches slower than engines that index every field.
  • A managed log service removes cluster upkeep, yet ingest-based pricing can grow fast when a noisy service floods logs.

Common mistakes

  • Shipping debug-level logs from every service by default and paying to store data nobody ever queries.
  • Forgetting to scrub tokens and passwords from log lines before they reach a shared central store.
Decision resources

Continue the technical evaluation

Use the resources that match your decision stage. Profile data and linked sources were refreshed through November 11, 2026.

Evaluation methodology · Corrections process