Linking LogicMonitor as a source
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.
This source is currently in alpha. The interface and available tables may change.
Connect your LogicMonitor account to sync alerts, devices, collectors, scheduled downtimes, and more into the PostHog data warehouse.
Prerequisites
You need a bearer token from your LogicMonitor portal:
- In LogicMonitor, go to Settings > Users & Roles > API Tokens > Bearer.
- Create a new bearer token.
- Give the token's user view permission for the resources you want to sync:
| Table | Required permission |
|---|---|
alerts | Resources |
devices | Resources |
device_groups | Resources |
collectors | Collectors |
sdts | Dashboards |
websites | Websites |
You only need to grant permissions for the tables you plan to sync.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to LogicMonitor.
- Enter your Portal URL – this must be an HTTPS URL and a direct subdomain of
logicmonitor.com(for examplehttps://example.logicmonitor.com). - Enter your Bearer token.
- Click Next.
- Select the tables you want to sync, set the sync frequency, then click Import.
Once the syncs are complete, you can start using LogicMonitor data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
alerts | Alerts for monitored resources, including active and cleared alerts within the account's retention period | Full refresh |
devices | Monitored device inventory and collector assignments | Full refresh |
device_groups | Groups that organize monitored devices | Full refresh |
collectors | Collectors, their availability, and the number of devices they monitor | Full refresh |
sdts | Scheduled downtime for resources and monitoring components | Full refresh |
websites | Website monitors and their alert settings | Full refresh |
Full refresh tables reload all data on each sync.
Sync limitations
- All tables use full refresh. Alerts use full refresh because an incremental watermark would miss later acknowledgments and clear events on older alerts.
- Inventory syncs exclude certain sensitive fields such as device properties, collector tokens, and collector configuration.
- A sync fails if a one-second time window contains more than 10,000 alerts. Contact support if you need to export dense alert history.
Configuration
| Option | Type | Required |
|---|---|---|
Portal URL | text | Yes |
Bearer token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
alerts | Alerts for monitored resources, including active and cleared alerts within the account's retention period. | Full refresh | — | — |
devices | Monitored device inventory and collector assignments. | Full refresh | — | — |
device_groups | Groups that organize monitored devices. | Full refresh | — | — |
collectors | Collectors, their availability, and the number of devices they monitor. | Full refresh | — | — |
sdts | Scheduled downtime for resources and monitoring components. | Full refresh | — | — |
websites | Website monitors and their alert settings. | Full refresh | — | — |