Log Monitoring - via FSO Agent

Log Monitoring - via FSO Agent

Applications Manager · AppLogs
Centralized log monitoring through the FSO Agent
Collect, parse, index and search application and server logs from one page, alongside metrics and traces.
60+
predefined log types
FSO Agent
log collector
7–90 days
search retention
Per GB
add-on licensing by volume

Overview

AppLogs is the log management capability of Applications Manager. It collects, parses, indexes and searches application and server logs from one search page, alongside metrics and traces. Logs are collected by the Full Stack Observability (FSO) Agent (source).

ℹThe standalone APM Insight agent collects only performance metrics. The FSO Agent covers server monitoring, APM Insight and AppLogs together. AppLogs requires an additional Add-On License, based on log ingestion volume.
ItemDetail
CollectorAppLogs sub-agent inside the FSO Agent
Predefined log types60+ (IIS, Apache, Windows Event Logs, Kubernetes, MySQL, PostgreSQL, SQL Server, middleware)
Custom log typesSupported, for non-standard or proprietary formats
Trial“Try Now” from v180700: one-time, 5 GB default limit, no reactivation
Primary use casesTroubleshooting and RCA, compliance and audit, security events, performance analysis

Module architecture

Logs travel from a sub-agent on each monitored server to the Applications Manager server, where they are parsed, indexed and stored locally.

Logs are indexed and stored on the Applications Manager server
Monitored serverApplications Manager server
AppLogs sub-agent
In the FSO Agent
Reads profile paths
Receive logs
→
Parse
Format set by the
log type
→
Index
Faster search
and retrieval
↓
↗
↙
Filter and batch
Source line filter
Upload 30 s or 40 MB per log type
AppLogs Search
Query and filter
by time and field
←
Local store
Zip every 7 days
Kept 7 to 90 days
→
Usage alerts
Warning at 80%
per log type

The agent filters and batches at source. The server then reads the uploads, parses by log type, indexes, and serves search and usage alerts from the same store (user guide, FSO Agent guide, FAQ).

ModuleRole
FSO AgentUnified agent on the Windows or Linux server (from v175500); sends performance data every 5 minutes
AppLogs sub-agentLog collector inside the FSO Agent; enable at install or under Settings › FSO Agent › SubAgents (Enable, Disable, Restart, Upgrade, Report)
Log typeWhat to fetch format definition used to parse entries (60+ predefined or custom)
Log profileWhere to fetch links a log type to file paths and servers; sets retention and collection limits
AppLogs ConfigurationLog Profiles, Log Types and Settings tabs: global retention, zip interval, read interval, warning threshold
AppLogs SearchKeyword and field search; filter by time, source, host, severity and response code

Onboarding flow

1
Deploy FSO Agent
With the AppLogs feature
→
2
Enable AppLogs
Sub-agent
→
3
Select / create Log Type
What to fetch
→
4
Configure Log Profile
Where to fetch; log type syncs to associated servers
→
5
Search and analyze
Logs persisted per retention

Supported search operators

CategoryOperators
Logicaland, or
Comparisonequals, !=, <, >, <=, >=
Text matchcontains, notcontains, startswith, like
Setin, notin
Empty checkIsEmpty, IsNotEmpty
Aggregationcount, count_distinct, sum, min, max, avg, sd
Grouping and limitsgroupby, timeslice, limit
Pipe|

Sample use cases

Ready-to-use AppLogs search queries for common troubleshooting scenarios. Replace the sample values (transaction ID, service, server) with your own.

1
Troubleshooting a failed checkout transaction
Trace one transaction end to end
3 queries
Search logs for a specific transaction
logtype="Application Log" and txnId EQUALS "TXN123456"
Identify failed checkout attempts
logtype="Application Log" and txnId EQUALS "TXN123456" and status EQUALS "FAILED"
Find errors related to the transaction
logtype="Application Log" and txnId EQUALS "TXN123456" and loglevel EQUALS "ERROR"
2
Identifying application errors after deployment
Spot regressions right after a release
3 queries
Find all error logs
logtype="Application Log" and loglevel EQUALS "ERROR"
Search for exception events
logtype="Application Log" and message CONTAINS "Exception"
Filter errors from a specific service
logtype="Application Log" and service EQUALS "payment-service" and loglevel EQUALS "ERROR"
3
Investigating web server access failures
Find failing requests in access logs
4 queries
Find HTTP 500 errors
logtype="Apache Access Log" and status EQUALS "500"
Find HTTP 404 errors
logtype="Apache Access Log" and status EQUALS "404"
Investigate errors for a specific endpoint
logtype="Apache Access Log" and endpoint CONTAINS "/checkout" and status EQUALS "500"
Identify errors from a specific server
logtype="Apache Access Log" and status EQUALS "500" and server EQUALS "web-server-03"
4
Troubleshooting microservices communication issues
Follow a request across services
3 queries
Trace a request across services
logtype="Application Log" and requestId EQUALS "REQ789123"
Find failures related to the request
logtype="Application Log" and requestId EQUALS "REQ789123" and loglevel EQUALS "ERROR"
Identify timeout or communication errors
logtype="Application Log" and message CONTAINS "timeout"

Persistence layer

AppLogs data lives on the Applications Manager server itself: logs are parsed and indexed, then compressed on local disk. Search is served from that index. Retention, not licence, drives disk use (retention KB, configuration guide).

SettingBehaviour
Global retention7 15 30 60 or 90 days; expired logs are deleted automatically
Per log type retentionOverrides global value via Search Retention (days) on the log type
Zip indexed data everyCompresses indexed data; default every 7 days
Read AppLogs data everyServer pulls agent data; recommended 2 min (min 1, max 5)
Agent uploadEvery 30 seconds or 40 MB per log type, whichever comes first (FAQ)
Disabling the sub-agentStops new collection; existing data stays until retention expires
Usage alertsWarning threshold default 80% per log type; optional email on Warning, Critical or Clear
ℹRetention beyond 90 days (for example 6 months or more for compliance): the GUI currently limits retention to 90 days. Longer retention is technically possible but is restricted for scalability reasons. An increase is planned, based on requirements and internal scalability validation.

Licensing

AppLogs is licensed by log volume uploaded per monthly billing cycle, in GB. It is separate from the monitor-based Applications Manager licence (FAQ).

  • AppLogs is available as an add-on.
  • Licensing is based on log size.
  • Retention is based on configuration within allowed limits (maximum 90 days).
QuestionAnswer
What is metered?GB of log data uploaded in the billing cycle
Does retention affect consumption?No; only uploaded volume counts
When does the limit reset?Automatically at the start of each billing cycle
What if the monthly limit is exhausted?New logs are not uploaded until the next cycle, or the limit is extended with add-ons
Trial without licence“Try Now” from v180700: 5 GB default, one-time, cannot be reactivated (user guide)
Support contact for add-onsappmanager-support@manageengine.com
✔To purchase or extend the AppLogs add-on license, visit the ManageEngine Store.

Prerequisites

✔AppLogs add-on license, sized by log volume in GB.
✔FSO Agent on each application server. Minimum specs: 1 GHz CPU 512 MB RAM 250 MB disk on Windows or 500 MB on Linux.
✔Outbound TCP from the application server to the Applications Manager port (default 10099).
✔Applications Manager storage and memory based on log volume and retention; see the Applog System Requirements and the Scalability section below.

Scalability

AppLogs scales on the Applications Manager server’s disk, not its memory: storage grows with monthly upload and retention, while AppLogs memory is capped at 320 MB (system requirements).

Storage is calculated per log type, then summed:

Storage (GB) = (Monthly upload (GB) ÷ 30) × Retention (days) × 0.5
Monthly upload7 days15 days30 days60 days90 days
50 GB5.83 GB12.5 GB25 GB50 GB75 GB
100 GB11.67 GB25 GB50 GB100 GB150 GB
250 GB29.17 GB62.5 GB125 GB250 GB375 GB
500 GB58.33 GB125 GB250 GB500 GB750 GB
1 TB116.67 GB250 GB500 GB1 TB1.5 TB
✔Memory is 64 MB per log type, capped at 320 MB (5 or more log types).

Ingestion controls

  • Agent upload is batched every 30 seconds or 40 MB per log type.
  • The server reads agent data every 1 to 5 minutes (recommended 2).
  • Unwanted lines can be filtered at source on the log type (for example by Windows EventID) to cut volume and licence use.
  • Per log type usage alerts start at an 80% warning threshold.

Roadmap

AppLogs dashboardImmediate
Cloud logs monitoring via endpoint and API ingestionPlanned
Logs-based reporting with cross-module integrationsPlanned
Retention beyond 90 days, based on requirements and scalability validationPlanned
Logs discoveryPlanned
Failover support: configurable storage redundancy on a network shared diskPlanned
Reporting capabilities: export of filtered logsPlanned

Delivered, per public documentation:

VersionMilestone
v175500FSO Agent (server monitoring agent) introduced (FSO Agent guide)
v179400AppLogs available as an FSO Agent sub-agent (user guide)
v180700“Try Now” limited trial for registered users without a licence
Listed in What’s new“Centralized AppLogs monitoring” (What’s new)

References