---
name: logs-java
description: PostHog log ingestion for Java applications via OpenTelemetry: configures an OTLP log exporter pointed at PostHog's ingest endpoint using environment variables for keys and endpoints, alongside existing logging code. Covers installation, log search, best practices, session replay linking, and troubleshooting. Use when adding PostHog logs to a Java app, sending Java application logs to PostHog, or debugging Java log ingestion.
license: MIT
---

# PostHog logs for Java

This skill helps you add PostHog log ingestion to Java applications.

## Reference files

- `references/java.md` - Java logs installation - docs
- `references/start-here.md` - Getting started with logs - docs
- `references/search.md` - Search logs - docs
- `references/best-practices.md` - Logging best practices - docs
- `references/troubleshooting.md` - Logs troubleshooting - docs
- `references/link-session-replay.md` - Link session replay - docs
- `references/debug-logs-mcp.md` - Debug logs with mcp - docs

Consult the documentation for API details and framework-specific patterns.

## Key principles

- **Environment variables**: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.
- **Minimal changes**: Add log export alongside existing logging. Don't replace or restructure existing logging code.
- **OpenTelemetry**: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.
- **Structured logging**: Prefer structured log formats with key-value properties over plain text messages.

## Framework guidelines

_No specific framework guidelines._