Sumo Logic

Sumo Logic

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more
PostHog Wizard hedgehog

Connect Sumo Logic to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.

Connect your Sumo Logic account to sync log search results, collectors, monitors, dashboards, users, and more into the PostHog Data warehouse.

Create an access ID and access key in your Sumo Logic preferences (or use a service account's access key). Pick the deployment region your account lives on — it's the subdomain of your Sumo Logic URL (e.g. service.eu.sumologic.com is the EU deployment).

The logs table runs your log search query through the Search Job API over rolling time windows. Leave the query as * to sync everything, or narrow it (e.g. _sourceCategory=prod/api) to control volume.

Configuration

OptionTypeRequired
Deployment regionselectYes
Access IDtextYes
Access keypasswordYes
Log search querytextareaNo

Linking Sumo Logic to PostHog

  1. Go to the Data pipeline page in PostHog
  2. Click New source and select Sumo Logic
  3. Fill in the required configuration fields
  4. Click Next, select the tables you want to sync, and then press Import

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
logs

Raw log messages matching your search query. Only syncs the last 7 days on initial sync

Incremental, Full refreshmessage_time
users

Users in your Sumo Logic organization.

Full refresh
roles

Roles in your Sumo Logic organization and the capabilities they grant.

Full refresh
collectors

Installed and hosted collectors that ingest data into Sumo Logic.

Full refresh
collector_sources

Data sources configured on each collector, one row per source with its parent collector id.

Full refresh
dashboards

Dashboards in your Sumo Logic organization.

Full refresh
monitors

Alerting monitors configured in your Sumo Logic organization.

Full refresh
partitions

Partitions that route your log data into separate indexes.

Full refresh
ingest_budgets

Ingest budgets that cap daily data ingestion volume.

Full refresh
connections

Outbound connections (webhooks) used by monitors and scheduled searches to send notifications. Credential-bearing fields (the destination URL, headers, and default payload) are dropped on import.

Full refresh
field_extraction_rules

Field extraction rules that parse fields out of messages at ingest time.

Full refresh
scheduled_views

Scheduled views that pre-aggregate log data into indexed views.

Full refresh
health_events

Health events reporting operational issues with collectors, sources, and ingest budgets.

Full refresh