kubeshark/telemetry

Telemetry - Iteration II

Opened this issue · 4 comments

alongir commented
  • Share with Mert

Use Elastic Search to store telemetry

  • Open a corporate Elastic search account
  • Assign the account to Alon
  • Open a PR
  • Move the current data to ES - no longe required
  • Create an initial dashboard

Revise telemetry information

  • Memory
  • CPU
  • No of CPUs
  • Amount of available memory
  • Packer received
  • Packet dissected
  • Cluster deployment identifier
  • License (email in the license)

Disable with air-gapped feature

  • Introduce an air-gapped value
  • When air-gapped feature is ON, heart-beat should be disabled (same as authentication and kernel module api calls).
  • This value is adhered to only when the edition is ENTERPRISE

Heartbeat

  • When telemetry is disable, we still send a heart-beat from each service only without the telemetry data.
  • If the user has a license, the license should be used to authenticate the telemetry API call
manfioLP commented

invite sent to alon@kubehq.io

manfioLP commented

to move current data to ES we will need to write a lambda to write from dynamo to Elasticsearch in bulk, but I'm checking with support other options...

manfioLP commented

currently changing our API Gateway to support Unique IP identifiers