Skip to content

Overview

The Reporting scope of the Controlplane currently features the following components:

  • dstoredist: Distribution, filtering, conversion and storage of DNS traffic protobuf messages generated by dnsdist & recursor
  • Event Forwarder: Used to store events related to DNS filtering in Elastic/Opensearch. These can then be retrieved/searched by the Report API
  • Report API: Used to retrieve reports about events related to DNS filtering from Elastic/Opensearch
  • TopN Reporter: Generation of reports based on protobuf messages received & distributed by dstoredist

When all components are deployed, it is possible to use complex topologies as shown in the following diagram:

Image title
Overview showing all dstore components

In the above diagram you see:

  • dnsdist & Recursor sending protobuf messages to a dstoredist within the Userplane
  • dstoredist in the Userplane forwarding messages to dstoredist in the Controlplane
  • dstoredist in the Controlplane storing in/sending data to 5 different destinations:
    • Storing via a WebSub endpoint
    • Storing in an S3 bucket
    • Storing in a Kafka cluster
    • Sending to TopN Reporter
    • Sending to Event Forwarder
  • Event Forwarder and TopN Reporter both receive data from dstoredist and after processing store their output in Elastic or Opensearch
  • Report API configured to expose reports stored in Elastic or Opensearch