Core concepts

Destinations

Destinations are custom endpoints or integrations that you wish to route data to.


Creating Destinations

New destinations can be generated within your dashboard. You may choose to create either a custom endpoint as a destination or leverage one of the existing integrations natively supported within ProxyHook. Currently our integrations include:

  • Clickhouse
  • AWS Redshift
  • Redis
  • AWS Cloudwatch Logs
  • AWS Kinesis Firehose
  • AWS Kinesis Streams
  • AWS S3
  • AWS SQS
  • Datadog Logs
  • ElasticSearch
  • Kafka
  • Plausible Analytics
  • Mixpanel
  • Customer.io

If using an integration you will be presented with a series of settings to handle various aspects of the integration such as authentication.


Activity

Within the dashboard you are able to view detailed breakdown of Destination Activity including:

  • Total number of requests
  • Number of requests with a 2XX status code reply
  • Number of requests with non 2XX status code reply
  • Number of filtered requests
  • Requests per second
  • Average execution time per request

You are able to splice the data with custom intervals ranging from 30 minutes to 1 month.


Formatting

Proxyhook offers very powerful formatting features for all payloads routed through a Destination. With our format feature you are able to modify the payload body or headers based on the incoming payload itself.

Formatting can be useful for numerous cases including:

  • Excluding certain data (such as PII)
  • Adjusting the format to required structure for the destination
  • Optimizing bandwidth usage

We currently offer nearly a hundred different transformation methods so please refer to the Format section for more information.


Filters

By default, Destinations will collect any data that is connected to it from a Subscription and Source, regardless of its content or origin. If you'd like to add fine-grained controls to this, you are able to do so within the Filter section. Filters will not impact the Analytics within Source Activity but will cause the data to not flow through to Logs or the actual Destinations.

Filters can be applied against any of the following and support various conditions such as equals, includes, greater than, less than, etc.

  • City
  • State
  • Country
  • IP Address
  • Host
  • User Agent
  • Referer
  • Cookies
  • Payload Content

Logging

Optionally, you may enable Logging on a specific source and specify a sample rate to collect logs on. This is useful for setup, debugging or if you'd like to create custom Data APIs off a specific source. To set the sample rate and enable logs, simply head to the specific source and it's Logs.

Previous
Sources