Pindot

Integrations

Everything Pindot reads from, and where it can send what it finds. Every source is connected with read-only access, and nothing goes out until an administrator turns it on.

Databases1

  • Databases

    Asked in plain language, with read-only access.

    Pindot reads itRead-only

Logs and files3

  • Log files over SSH

    Read on the server where they are written. Nothing to install there.

    Pindot reads itRead-only
  • SFTP drops

    Files collected from a drop directory as they land.

    Pindot reads itRead-only
  • File upload

    A log file an operator drops into the console.

    Sent to Pindot

Streams2

  • Syslog

    Received on a port of its own, with the device's severity kept.

    Sent to Pindot
  • Webhooks

    Pushed by your monitoring, with a token for each source.

    Sent to Pindot

Service desk1

  • Ticketing systems

    Incidents and change records from your service desk, read as they change.

    Pindot reads itRead-only

APIs1

  • REST APIs

    Any JSON endpoint you describe, polled on a schedule.

    Pindot reads itRead-only

Destinations2

Off until an administrator turns it on.

  • Jira

    Tickets with the evidence pack, Cloud or Data Center.

    You review each ticket draft before it is filed.

    Pindot sends to it
  • Slack

    Findings and alert notifications.

    Findings are posted with their evidence attached.

    Pindot sends to it

Stop digging through logs at 2am.

Bring your own 02:14, a real incident from your systems. We will show you how Pindot finds the cause, and where every piece of evidence came from.