Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

EXPORT TELEMETRY

On this page

Writes usage telemetry data to a file.

This command generates the same usage telemetry data that is sent when the send_usage_telemetry engine variable is enabled, and is based off of the data in the usage_telemetry_status information schema table.

Syntax

EXPORT TELEMETRY TO 'file name' FOR PROD|QA|DEV|SANDBOX [FORCE]

Arguments

  • FORCE option will overwrite the file if it already exists.

  • FOR PROD|QA|DEV|SANDBOX specifies the type of cluster the report is for.

Remarks

EXPORT TELEMETRY honors the secure_file_priv engine variable which limits the directories to which SingleStore can write a file.

Example

Write usage telemetry data to a file called 'tel_dev_20240306' for a dev cluster:

EXPORT TELEMETRY TO '/tmp/tel_dev_20240306' FOR DEV;
Query OK, 0 rows affected (0.00 sec)

Last modified: July 30, 2024

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In