Sign inTry Free

Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

MV_TRACE_EVENTS

While the trace events can be viewed via the information schema MV_TRACE_EVENTS table, this buffer is not intended to be directly consumed by the end user. The PROCESS permission is required to query MV_TRACE_EVENTS.

The new information schema table represents semi-structured data to support any arbitrary event that occurs on a node. It also includes a JSON column for details specific to that event type. Queries against this table can also filter events using familiar SQL DML. Note that this is where event filtering happens. The DDL language used to create and configure trace events defines how an event is traced and may, depending on the options selected, result in some events not being traced.

Note that MV_TRACE_EVENTS is a ring buffer where the oldest events are overwritten when the buffer wraps around. To save events, other software (such as the Query History feature)  must gather them before they age out of MV_TRACE_EVENTS.

Column Name

Description

Column Type

NODE_ID

The ID of the SingleStore node

bigint(4)

NODE_IP

The IP address of the SingleStore node

varchar(256)

NODE_TYPE

The type of node: master aggregator (MA), child aggregator (CA), or leaf node (LEAF)

varchar(8)

NODE_START_EPOCH_S

The time the node started

bigint(20)

EVENT_ID

The event ID

bigint(20)

EVENT_TYPE

Query_completion

varchar(256)

TIME

Time when the event was traced in the buffer

datetime(6)

DETAILS

Refer to View MV_TRACE_EVENTS

JSON

The rows are returned approximately in ascending order of time, grouped individually by node. As there is no guarantee that an event that occurred at a specific time will be inserted into the ring buffer before an event that occurs later, events are not guaranteed to be returned in chronological order.

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