AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides guidance and reference materials for configuring Java applications to export logs to PostHog. It emphasizes the use of the OpenTelemetry protocol and structured logging practices to ensure logs are actionable and queryable. The skill covers installation, best practices for log structure, and methods for debugging and searching logs within the PostHog ecosystem.
What it does
- Provides instructions for setting up OpenTelemetry log exporters in Java.
- Outlines best practices for structured logging to improve queryability.
- Explains how to correlate logs with session replays and trace data.
- Offers guidance on troubleshooting log ingestion issues.
- Details how to use MCP tools to search and analyze logs directly from an IDE.
When to use it
- When you need to centralize logs from Java services into PostHog.
- When you want to transition from plain text logging to structured, wide events.
- When you need to debug production issues by correlating logs with user sessions or traces.
- When you are setting up observability for a new or existing Java application.
Advantages
- Enables unified visibility across logs, product analytics, and session replays.
- Promotes the use of standard OpenTelemetry protocols for vendor-neutral ingestion.
- Encourages structured logging patterns that reduce noise and improve searchability.
- Supports direct log querying and analysis within AI-enabled development environments.
Usage examples
- “How do I configure my Java application to send logs to PostHog?”
- The agent provides steps to configure an OTLP exporter in your Java application, pointing it to the PostHog ingest endpoint using environment variables.
- “Show me all error logs from the payments service in the last hour.”
- The agent uses the logs-query MCP tool to filter and display relevant error logs from the specified service.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/logs-java/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip logs-java.zip -d .agents/skills
Documentation by PostHog
PostHog logs for Java
This skill helps you add PostHog log ingestion to Java applications.
Reference files
references/java.md- Java logs installation - docsreferences/start-here.md- Getting started with logs - docsreferences/search.md- Search logs - docsreferences/best-practices.md- Logging best practices - docsreferences/troubleshooting.md- Logs troubleshooting - docsreferences/link-session-replay.md- Link session replay - docsreferences/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.
Files
- ATTRIBUTION.mdAdded by AutoGineer927 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md1.3 KiB
- references/best-practices.md19.6 KiB
- references/debug-logs-mcp.md2.2 KiB
- references/java.md3.9 KiB
- references/link-session-replay.md4.9 KiB
- references/search.md2.5 KiB
- references/start-here.md2.4 KiB
- references/troubleshooting.md3.5 KiB
references/java.md
Java logs installation - Docs
1
Install OpenTelemetry packages
Required
Add the following dependencies to your
pom.xml:XML
PostHog AI
<dependency> <groupId>io.opentelemetry</groupId> <artifactId>opentelemetry-api</artifactId> <version>1.32.0</version> </dependency> <dependency> <groupId>io.opentelemetry</groupId> <artifactId>opentelemetry-sdk</artifactId> <version>1.32.0</version> </dependency> <dependency> <groupId>io.opentelemetry</groupId> <artifactId>opentelemetry-exporter-otlp</artifactId> <version>1.32.0</version> </dependency>2
Get your project token
Required
You'll need your PostHog project token to authenticate log requests. This is the same key you use for capturing events and exceptions with the PostHog SDK.
Important: Use your project token which starts with
phc_. Do not use a personal API key (which starts withphx_).You can find your project token in Project Settings.
3
Configure the SDK
Required
Set up the OpenTelemetry SDK to send logs to PostHog.
Java
PostHog AI
import io.opentelemetry.api.logs.GlobalLoggerProvider; import io.opentelemetry.sdk.logs.SdkLoggerProvider; import io.opentelemetry.sdk.logs.export.BatchLogRecordProcessor; import io.opentelemetry.exporter.otlp.logs.OtlpHttpLogRecordExporter; SdkLoggerProvider loggerProvider = SdkLoggerProvider.builder() .addLogRecordProcessor( BatchLogRecordProcessor.builder( OtlpHttpLogRecordExporter.builder() .setEndpoint("https://us.i.posthog.com/i/v1/logs") .addHeader("Authorization", "Bearer <ph_project_token>") .build() ).build() ) .build(); GlobalLoggerProvider.set(loggerProvider);Alternatively, you can pass the API key as a query parameter:
Java
PostHog AI
OtlpHttpLogRecordExporter.builder() .setEndpoint("https://us.i.posthog.com/i/v1/logs?token=<ph_project_token>") .build()4
Use OpenTelemetry logging
Required
Now you can start logging with OpenTelemetry:
Java
PostHog AI
import io.opentelemetry.api.logs.Logger; Logger logger = GlobalLoggerProvider.get().get("my-app"); logger.logRecordBuilder() .setBody("User action") .setAttributes(Attributes.of( AttributeKey.stringKey("userId"), "123", AttributeKey.stringKey("action"), "login" )) .emit();5
Test your setup
Recommended
Once everything is configured, test that logs are flowing into PostHog:
Send a test log from your application
Check the PostHog logs interface for your log entries
Verify the logs appear in your project
Next steps
Checkpoint
What you can do with your logs
Action Description Why you need logs What logs show you that nothing else does Search logs Use the search interface to find specific log entries Filter by level Filter by INFO, WARN, ERROR, etc. Link session replay Connect logs to users and session replays by passing posthogDistinctId and sessionId Logging best practices Learn what to log, how to structure logs, and patterns that make logs useful in production
Community questions
Ask a question
Was this page useful?
HelpfulCould be better
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/logs/skills/java · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download logs-java.zip