From 70a9988c6b7e89d9d6ae6f7cfa058307dad95804 Mon Sep 17 00:00:00 2001 From: michael vincerra <37549381+mvincerx@users.noreply.github.com> Date: Wed, 10 Jul 2019 09:04:17 -0700 Subject: [PATCH] Add section on settign a static machine id. (#606) - Closes #558. Signed-off-by: Michael Vincerra --- .../guides/telemetrics/telem-guide.rst | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/source/clear-linux/guides/telemetrics/telem-guide.rst b/source/clear-linux/guides/telemetrics/telem-guide.rst index d9b7f089..6fdbad8e 100644 --- a/source/clear-linux/guides/telemetrics/telem-guide.rst +++ b/source/clear-linux/guides/telemetrics/telem-guide.rst @@ -356,7 +356,31 @@ There are three ways to supply the payload to the record. payload read from stdin +Set a static machine id +======================= +The machine id reported by the telemetry client is rotated every three days +for privacy reasons. If you wish to have a static machine id for testing +purposes, you can opt in by creating a file named "opt-in-static-machine-id" +in the directory :file:`/etc/telemetrics/`. + +#. Create a directory `telemetrics`. + + .. code-block:: bash + + sudo mkdir -p /etc/telemetrics + + +#. Create the file and replace the "unique machine ID" with your desired + static machine ID. + + .. code-block:: bash + + echo "unique machine ID" | sudo tee /etc/telemetrics/opt-in-static-machine-id + +.. note:: + + The `machine id` is different than the system hostname. Instrument your code with the libtelemetry API ==============================================