The goal of the collector is to support high volume data. It uses plain TCP connections.
Connections are stream-based (as opposed to request-based) and long running.
Payload is binary-encoded (currently using Google Protocol Buffers).
-HV-VES uses direct connection to DMaaP's Kafka.
+HV-VES uses direct connection to Kafka.
All these decisions were made in order to support high-volume data with minimal latency.
.. toctree::
:maxdepth: 1
-
+
architecture
design
- run-time-configuration
repositories
deployment
- troubleshooting
+ installation-helm
+ run-time-configuration
HV-VES Offered APIs <../../apis/ves-hv/index>
authorization
example-event
healthcheck-and-monitoring
+ troubleshooting