LimaCharlie¶
Collects endpoint detection and telemetry events from LimaCharlie, providing visibility into endpoint activity, detections, and sensor health across your LimaCharlie organization.
| Category | Infrastructure |
| Connector Name | signal-client.limacharlie |
| Auth Method | API Key (Bearer) + Organization ID |
| Polling Interval | 5 min (events) |
| Multi-Instance | Yes |
| Vendor Docs | LimaCharlie API Documentation |
Prerequisites¶
Vendor Requirements
Active LimaCharlie organization. Admin access required to generate API keys.
- Active LimaCharlie organization
- Admin access in the LimaCharlie web console
- Network: Conductor can reach
api.limacharlie.ioon port 443
Step 1: Create API Credentials¶
- Log in to the LimaCharlie Console at
https://app.limacharlie.io/ - Select your organization
- Navigate to Access Management → REST API
- Click Create API Key
- Configure the key:
- Name:
WitFoo Conductor - Permissions: Read access to detections and telemetry
- Name:
- Copy the API Key
- Note your Organization ID from the organization settings page
Store Credentials Securely
API keys grant access to your LimaCharlie telemetry data. Store them securely and do not share them in tickets or email.
Step 2: Configure in Conductor¶
- Open the Conductor UI at
https://<conductor-ip>/admin/settings/integrations - From the Add Integration dropdown, select LimaCharlie
- Enter a unique name for this instance
-
Fill in the settings form:
Field Value Description Host api.limacharlie.ioLimaCharlie API endpoint Organization ID <your-org-id>Organization ID from step 1 API Key <your-api-key>API key from step 1 -
Set the Polling Interval (recommended: 5 minutes)
- Toggle Enabled to on
- Click Save
Step 3: Validate Data Flow¶
After saving, verify the integration is working:
- Check connection status — The integration tile should show a green status indicator within 1–2 polling cycles
-
Check Signal Client logs:
Look for successful poll messages:
-
Check artifacts in Analytics — Navigate to the WitFoo Analytics Signals → Search page and search for artifacts from this source
First Poll Timing
The first data pull occurs within the configured polling interval after saving. For a 5-minute interval, expect data within 5 minutes.
Troubleshooting¶
Authentication Failed (401)¶
- Verify the API Key is correct and has not been revoked
- Ensure the Organization ID matches the key's organization
Forbidden (403)¶
- The API key may lack required permissions
- Ensure the key has read access to detections
Rate Limited (429)¶
- Increase the Polling Interval to 10 minutes
- Conductor automatically implements exponential backoff on 429 responses
No Data Appearing¶
- Confirm the integration shows Enabled in the Conductor UI
- Check Signal Client logs for errors:
docker logs signal-client-svc --tail=100 - Verify network connectivity:
curl -I https://api.limacharlie.io - Confirm events exist in the LimaCharlie console for the polling time window
See also: Integration Catalog · Integration Management · Signal Client · Common Troubleshooting