Organization Query Monitor — Block & Kill

The Block and Kill panel allows you to kill a currently running query or to block the execution of the query in the future.

Organization Query Monitor Block and Kill Panel

Figure 33. Organization Query Monitor Block and Kill Panel


Killing a Running Query

Killing a running query terminates the current execution. In general this option is used when you want to stop the query because it is taking too many resources or running for too long.

Before killing a query, check the Query Stats and Query Details panels to ensure that you are killing the correct query. Be aware that killing the query will block all executions of the query where it's used and may cause the output of widgets and automations to fail if they use the query.

To kill a query, select the query from Query Monitor panel. Then check the Query Stats and Query Details panels. When ready, click the Kill Query button.

A message will be displayed at the bottom of the page to indicate that the query has been killed.

Important

Streaming Aggregate Queries will not be shown in the list of running queries, and they are not canceled by the Stop Streaming Queries button. These queries can only be canceled by rebooting LogScale nodes.

Blocking a Query

When blocking a query using this panel, the query block that is added uses the full query string against the specific View or Repository that the currently selected query is executing against. This is identical to creating a text match query to a specific Repository within the Add Query to Blocklist page.

To block a query:

  1. Select the query from Organization Query Monitor panel that you want to terminate.

  2. Check the Query Stats and Query Details panels.

  3. Click the Block Query button.

A message will be displayed at the bottom of the page to indicate that the query has been blocked.

To manage blocked queries, visit the Blocklist page.