Integration
Java applications
Logback, Log4j and Spring Boot log files, parsed on the host with stack traces kept whole; add the OpenTelemetry Java agent for traces.
- Category: Applications
- How data is sent: Logthread Agent
- Runs on: Linux
- Status: Beta
How it works#
- Answer a few questions. They only fill in the setup steps. Nothing on this page connects to your servers: Logthread never reaches into your network.
- Run one command on the machine that writes the log. The next page shows the command with this connector's ingest key filled in. It downloads the Logthread Agent from downloads.logthread.com and installs it as a service (Linux, as root with sudo). No other download.
- Data arrives. Everything is collected inside your environment. It is sent over outbound HTTPS (port 443) to ingest.logthread.com. Nothing is opened to the internet: no inbound ports, VPN or public access to your servers. The connection page shows what has arrived and turns Active with the first record.
What you answer#
| Question | Answer | Notes |
|---|---|---|
| Log file (optional) | Text | Default: /var/log/app/*.log. |
| Service name (optional) | Text | Default: java. Use the application name, one connector per application. |
| Labels (optional) | Text | For Fleet and filtering, for example env=prod. |
| Manage this agent from Fleet | Yes or no | Change its configuration from Logthread later without logging in to the host. Default: Yes. |
Setup#
These are the steps for the default answers. In the app, they follow your answers, and the connector's ingest key replaces YOUR_INGEST_KEY.
Step 1. Install the Logthread Agent. On the machine that writes the log. It reads the file as the application appends to it, keeps a stack trace with the line that logged it, and sends over outbound HTTPS. Logback and Log4j default patterns and the Spring Boot pattern are recognised as they are; another pattern still arrives, as whole lines, for a parser of your own.
curl -sSL https://downloads.logthread.com/agent/install.sh | sudo sh -s -- \
--key YOUR_INGEST_KEY --profiles java-logs --fleetStep 2. Wait for data. Lines appear within seconds of being written. Traces and metrics come separately from the OpenTelemetry Java agent pointed at the same key (Developers, OpenTelemetry).
Check that it works#
The connection page under Integrations counts what has arrived and turns Active with the first record. In Explore, search service:java.
Then add#
Each is one click on the connection page and opens with your data, so you can check it before saving.
- Parser: java-logback (Pipelines → Library)
- Alert: Java exceptions:
service:java exception.stacktrace:*, at least 5 in 10 minutes - Alert: Java errors:
service:java severity:(error|fatal), at least 10 in 10 minutes
Set it up under Integrations in the app, or from an AI agent with MCP (add_integration). All integrations: Integrations guide. Next: find what it sends in Explore and live tail.