AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

omnibus-instrument-logs

Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--omnibus-instrument-logs at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 14

references/other.md

Other languages logs installation - Docs

PostHog logs works with any OpenTelemetry-compatible client. Check the OpenTelemetry documentation for your specific language or framework.

  1. 1

    Install OpenTelemetry packages

    Required

    The key requirements are:

    • Use OTLP (OpenTelemetry Protocol) for log export over HTTP
    • Send logs to your PostHog logs endpoint (see configuration step below)
    • Include your project token in the Authorization header or as a ?token= query parameter

    Find the OpenTelemetry SDK for your language in the official registry.

  2. 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 with phx_).

    You can find your project token in Project Settings.

  3. 3

    Configure the SDK

    Required

    Configure your OpenTelemetry SDK to send logs to PostHog.

    Endpoint:

    PostHog AI

    https://us.i.posthog.com/i/v1/logs
    

    Authentication: Include your project token either as an Authorization header:

    PostHog AI

    Authorization: Bearer <ph_project_token>
    

    Or as a query parameter on the endpoint:

    PostHog AI

    https://us.i.posthog.com/i/v1/logs?token=<ph_project_token>
    
  4. 4

    Test your setup

    Recommended

    Once everything is configured, test that logs are flowing into PostHog:

    1. Send a test log from your application
    2. Check the PostHog logs interface for your log entries
    3. Verify the logs appear in your project

    View your logs in PostHog

  5. 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 |

    Troubleshoot common issues

Community questions

Ask a question

Was this page useful?

HelpfulCould be better