AppLogs is a log management capability in Applications Manager that enables you to collect, ingest, search, and analyze logs from applications and servers through a single, unified search interface. Logs are collected using the Applications Manager Full Stack Observability (FSO) Agent and are presented in a centralized view, making it easier to correlate and analyze log data across your environment.
Log monitoring, along with metrics and traces, is a core pillar of observability. AppLogs helps teams gain deeper visibility into system behavior, troubleshoot issues faster, and maintain operational, compliance, and security standards.
Note: The AppLogs feature is supported from Applications Manager v179400 and above.
AppLogs helps you gain actionable insights from logs for the following use cases:
AppLogs collects logs from monitored servers through the Applications Manager FSO Agent. Once logs are collected, they are:
This enables you to view and analyze logs from multiple applications and servers in one centralized interface.
To start using AppLogs in Applications Manager, follow the steps below to configure log collection and analysis:
) under the Actions column for an individual agent, or use the Bulk Actions option to enable it for multiple agents at once.Once these steps are completed, AppLogs automatically begins collecting logs and makes them available for searching, filtering, and analysis through the AppLogs Search page.
AppLogs is deployed as a sub-agent within the Full Stack Observability (FSO) Agent of Applications Manager. Once enabled, the AppLogs sub-agent allows Applications Manager to collect and monitor logs from applications and services running on the server.
You can view and manage the AppLogs sub-agent status from the FSO Agent management pages in the Applications Manager UI. The status indicates whether the sub-agent is enabled and shows the last communication time with the server.
To enable the AppLogs sub-agent for an existing/onboarded FSO Agent, follow the steps below:
) of an agent to open the Sub Agent Management panel.Once enabled, the AppLogs sub-agent begins reading and forwarding log data from the corresponding servers.
For more information on deploying and managing FSO Agents and sub-agents, refer to the FSO Agent documentation.
A log type defines the format in which an application writes its logs.
Different applications—such as IIS, Apache, Cassandra, and MySQL—generate logs in different formats. Defining these formats as log types helps AppLogs:
If an application’s log format is not available by default, you can create a custom log type to suit your requirements.
AppLogs includes 60+ predefined log types for commonly used platforms and services, including:
These predefined log types allow you to start collecting and analyzing logs quickly with minimal configuration.
Custom log types allow you to define log formats for applications or services that generate logs in non-standard or unique formats.
This is especially useful in environments such as:
By defining a custom log type, you ensure that logs are parsed correctly and remain searchable and easy to analyze.
A log profile associates a log type with specific log sources such as files or directories.
Log profiles define:
Using log profiles, you can efficiently manage log collection across multiple servers and applications.
AppLogs provides powerful search and filtering capabilities to help you analyze logs effectively. You can:
These capabilities help you move from raw log data to meaningful, actionable insights.
In Applications Manager, AppLogs monitoring can be stopped only by disabling the AppLogs sub-agent on the required servers. Existing log data is retained and not removed.
You can disable the AppLogs sub-agent from the FSO Agent management page by navigating to AppLogs → Deploy Agent → selecting the SubAgents option for an agent, and clicking Disable.
Once disabled, the agent stops reading and sending log data from the corresponding servers.
Thank you for your feedback!
