Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

Logs

To monitor the progress of your extracts and loads, navigate to the Logs tab. The log displays the progress and current activity of the Ingest instance. You can apply filters to view specific logs, such as errors. You can view the logs of the following:

  • Source: Displays the logs of the source database.

  • Destination: Displays the logs of the destination database.

  • Others: Displays the logs of the Ingest instance.

  • Errors: Displays all errors related to the source, destination, and Ingest instance.

Ingest stores log files in the install folder, under the \log folder. The path to the log files is: <install folder of Ingest>\log\sirus*.log. For example, c:\SingleStore-Flow\Ingest\log\sirus-2019-01.log.

Error files are also stored in the \log folder. The path to these error files is: <install folder of Ingest>\log\error*.log. For example, c:\SingleStore-Flow\Ingest\log\error-2019-01.log.

These logs can also be reviewed or stored in S3. Refer to Remote Monitoring for more information.

Last modified:

Was this article helpful?

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