Log Monitoring Troubleshooting FAQ | Qntrl Online Help | Troubleshoot Log Monitoring Issues

System Logs Troubleshooting FAQ

1. Why are no logs returned for my query?  

If a query does not return any results, verify the following:

  • The selected Log Type is correct.

  • The selected Module is not mismatched with the component being investigated.

  • The Status filter or query condition is configured correctly.

  • The selected time range includes the expected execution.

  • The logs have been indexed and are available for search.

Newly generated logs may take a few minutes to become searchable.  


2. Why can't I find recently generated logs?   

Log data is indexed before it becomes searchable. As a result, newly generated logs may not appear immediately. Wait a few seconds and execute the query again.

3. Why am I not seeing auto-suggestions while typing?   

Auto-suggestions are displayed only for supported log types, fields, operators, and values.

If suggestions do not appear:

  • Verify that the query syntax is valid.

  • Ensure the selected log type supports the field being queried.

  • Continue typing additional characters to narrow suggestions.

For supported query syntax, refer to Auto-Suggestions and Query Language.


4. Why does my query return unexpected results?   

Unexpected results may occur when:

  • An incorrect log type is selected.

  • The query contains unsupported field names.

  • Conditions are combined incorrectly.

  • The selected time range is too broad or too narrow.

Review the generated query and verify all selected filters.


5. Why can't I find logs for a specific execution?   

  To investigate a specific execution:

  1. Search using the appropriate log type.

  2. Open the matching log entry.

  3. Use View Trace Tree to identify related executions.

  4. Use the qthread_id to locate all logs associated with the execution flow.

   

6. How do I identify what triggered an execution?   

  1.   Open the log entry and select View Trace Tree.

  2. Use Open Parent to view the component that initiated the current execution.

  3. You can also use the parent_access_id to identify the immediate parent execution.

 

Use the QThread ID available in the log details.

Use the qthread_id to trace all logs that belong to the same execution flow. To understand direct parent-child relationships between executions, use the parent_access_id .

Refer to Trace Logs using QThread ID and Trace Parent Executions using Parent Access ID for details.

 

 The View Related Logs action is available only for script-based modules such as:

  • Functions

  • CodeX

For other modules, related application logs may not be available.


9. Why can't I find the execution that generated a logger message?   

When searching for a logger message:

  1. Open the matching Application Log.

  2. Click View Application Logs icon .

  3. Open the associated Access Log or Execute Log.

This helps identify the execution that generated the message.  


10. Why can't I update a saved query?   

Only the query name can be edited after a query is saved.

If you modify the query definition, it must be saved as a new query.


11. Why is an alert not being triggered?   

Verify that:

  • The alert is enabled.

  • The query condition matches incoming log data.

  • New logs satisfy the configured alert criteria.

Review the alert configuration and ensure the underlying query returns the expected results.

    • Related Articles

    • Bridge Troubleshooting FAQs

      1. Prerequisites & System Requirements 1.1 What are the prerequisites for installing and using Qntrl Bridge? Before installing Qntrl Bridge, ensure the following prerequisites are met: Administrative (Windows) or sudo (Linux/macOS) privileges are ...

    • User Logs

      Early Access This feature is not enabled for all users. If you'd like to try it out, please email our support team for early access. User Logs can be used to individually manage and track the activity of your organization’s users in Qntrl. User logs ...

    • Execution Logs

      A record of all tested executions is maintained in Circuit, allowing you to access and re-run specific executions anytime. Follow these steps to access the execution history of a circuit: Access Execution History Go to the left pane and click on the ...

    • Manage Audit Logs

      Audit Log helps you monitor the activities performed in your Qntrl organization. It allows you to track the changes carried out in different modules of Qntrl individually. Along with the actions executed by users, you can also view logs for automated ...

    • Troubleshooting FAQ

      1. Why is my WebSocket not connecting? Check if the endpoint URL is correct Verify the Authentication Type(OAuth/API Key) Ensure the connection is not blocked by network/firewall 2. Why are messages not being processed? Verify the Resource Selection ...