WitFoo Conductor collects security log data from cloud platforms, endpoints, identity providers, email security, network infrastructure, and more through pull-based API integrations. The Signal Client service polls each vendor's API on a configurable schedule and publishes artifacts to the processing pipeline.
Looking for log shippers / agents?
For push-based collection from Elastic Beats agents (Filebeat, Winlogbeat, Packetbeat — OSS builds), see the Log Shippers (Beats) guides. Those agents stream to the Signal Server over TCP 5044/5045 rather than being polled by the Signal Client.
Security platforms that push syslog, such as Nozomi Networks and Dragos, have their own Syslog Sources guides.
Polling Interval — Built into each connector and not configurable; each guide lists its connector's interval. Splunk is the exception: its form has a Poll Interval field (seconds)
Checkpoint Tracking — Signal Client resumes from the last successful position after restarts, avoiding duplicate collection
Rate Limiting — Built-in respect for vendor API quotas with exponential backoff on HTTP 429 responses
Enable/Disable — Each integration can be toggled without removing its configuration
Configuration changes propagate within seconds via the NATS KV watch mechanism. No container restart is required.