Using TelemetryGen to send data to MDAI Cluster

Why use TelemetryGen?

Using TelemetryGen is a great option if you're not ready to commit to the costs associated with ingress/egress to your cluster. It's all local to the cluster you have just deployed, so there will not be additional charges, minus the compute required to generate and process the telemetry.

Let's begin!

In our example we'll

  1. Create or use an existing cronjob or job
  2. Apply the cronjob/job to your cluster
  3. Watch telemetry flow through the console
  4. Destroy the cronjob/job
  5. Eat cake!

Step 1 - Create or use cronjobs

You can create a CronJob (or use one from the /jobs directory).

Step 2 - Apply the cronjob to your cluster

kubectl apply -f <cron_filename.yaml>

Step 3 - Validate job is running

Via kubectl

# Get job by name - replace job-name with your cronjob's name
kubectl get cronjob job-name

# Still not enough? Watch your cronjob using the --watch command
kubectl get cronjob --watch

At this point, you should also be able to see data flowing through the MDAI Console to validate data flow.

Step 4 (optional, recommended) - Delete the cronjob once testing is complete

# Delete job by name - replace job-name with your cronjob's name
kubectl delete cronjob job-name
It is critical that you delete the cronjob once testing is complete, otherwise MDAI Cluster costs will continue to increase as the MDAI Cluster continues to processes all incoming telemetry data.

Step 5 - Eat cake 🍰!

You sent your first telemetry record to MDAI!

🎉 That's it! Your MDAI Cluster is now ready to use! 🎉

Want more ways to send your cluster data?

Still curious about the other ways to generate and send telemetry?


⏪ Back to Intro: Generate and Receive Telemetry