InsightIDR

Custom Logs

Like other raw data, custom logs contextualize information throughout InsightIDR and are helpful during log search.

Any text based log of any kind can be ingested through InsightIDR. This event source will accept any data as is and does not parse. As such, use this event source when you want to send data in a format that is not current supported by the platform.

How to Configure This Event Source

  1. From your dashboard, select Data Collection on the left hand menu.

  2. When the Data Collection page appears, click the Setup Event Source dropdown and choose Add Event Source.

  3. From the “Raw Data” section, click the Custom Logs icon. The “Add Event Source” panel appears. 

  4. Choose your collector and event source. You can also name your event source if you want.

  5. Choose the timezone that matches the location of your event source logs.
  6. Optionally choose to send unfiltered logs.
  7. Configure inactivity timeout threshold in minutes.
  8. Select a collection method and specify a port and a protocol.
    • Optionally choose to Encrypt the event source if choosing TCP by downloading the Rapid7 Certificate.
  9. Click Save.

Custom Log Recommendations

Rapid7 recommends using JSON or KVP format for logging, as data is presented in log search in this form. Sending an unstructured string will yield an unstructured log entry in InsightIDR - you can search for any text in the event, but lose the benefit of keyword search.

Formatting logs in JSON or KVP will allow InsightIDR to preserve the keyword format and provide the added benefit of keyword search (eg, foo=bar).


Custom Logs


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.