🚫 🔍 [Deprecated] Apache Tomcat
🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | ApacheTomcat |
| Publisher | Apache |
| Used in Solutions | Tomcat |
| Collection Method | MMA |
| Connector Definition Files | Connector_Tomcat_agent.json |
The Apache Tomcat solution provides the capability to ingest Apache Tomcat events into Microsoft Sentinel. Refer to Apache Tomcat documentation for more information.
Additional Information
🛠️ Device Configuration: Table: Tomcat_CL. Log location (Linux): /var/log/tomcat/*.log. See Custom Logs via AMA configuration.
Tables Ingested
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
Tomcat_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions: - Workspace (Workspace): read and write permissions are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias TomcatEvent and load the function code or click here.The function usually takes 10-15 minutes to activate after solution installation/update.
NOTE: This data connector has been developed using Apache Tomcat version 10.0.4
1. Install and onboard the agent for Linux or Windows
Install the agent on the Apache Tomcat Server where the logs are generated.
Logs from Apache Tomcat Server deployed on Linux or Windows servers are collected by Linux or Windows agents. Choose where to install the Linux agent:
Install agent on Azure Linux Virtual Machine
Select the machine to install the agent on and then click Connect. - Install agent on Linux Virtual Machine
Install agent on a non-Azure Linux Machine
Download the agent on the relevant machine and follow the instructions. - Install agent on Linux (Non-Azure)
Choose where to install the Windows agent:
Install agent on Azure Windows Virtual Machine
Select the machine to install the agent on and then click Connect. - Install/configure: InstallAgentOnVirtualMachine
Install agent on a non-Azure Windows Machine
Download the agent on the relevant machine and follow the instructions. - Install/configure: InstallAgentOnNonAzure
2. Configure the logs to be collected
Configure the custom log directory to be collected - Open custom logs settings
- Select the link above to open your workspace advanced settings
- From the left pane, select Data, select Custom Logs and click Add+
- Click Browse to upload a sample of a Tomcat log file (e.g. access.log or error.log). Then, click Next >
- Select New line as the record delimiter and click Next >
- Select Windows or Linux and enter the path to Tomcat logs based on your configuration. Example: - Linux Directory: '/var/log/tomcat/*.log'
- After entering the path, click the '+' symbol to apply, then click Next >
- Add Tomcat_CL as the custom log Name and click Done
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊