AI Query Assistant

Overview

The Coralogix AI Query Assistant makes data querying easier. Describe what you're looking for in everyday language. The system will analyze your request and convert your description into a structured DataPrime query, saving you the trouble of writing complex queries.

Natural language to structured queries

The AI Query Assistant uses an advanced large-language model (LLM) to help you. You can enter your request in plain English, which is converted into a precise DataPrime query.

Disclaimer: LLM-based systems are still evolving, and the AI Query Assistant can make mistakes. That’s why, we recommend validating any DataPrime query before running it.

Flexible query modification

After you generate the query, you can review your prompt and adjust the generated DataPrime query to make the data exploration process more flexible.

Smart input evaluation

The AI Query Assistant minimizes the risk of DataPrime query errors. It detects and corrects spelling mistakes in the user prompt and prevents syntax or spelling errors in the DataPrime editor, ensuring more accurate and efficient data retrieval. In addition, the AI Query Assistant validates user entries, which must be within DataPrime scope. Invalid input is automatically rejected.

Prerequisites

The AI Query Assistant can be enabled or disabled by users with the dataprime-ai-query-assistant:Manage permission (Settings > Account Preferences > DataPrime AI Query Assistant).

Limitations

Currently, the AI Query Assistant is available for querying logs only.
The AI Query Assistant supports single-turn interaction only. This means that a session consists of one user prompt and one Query Assistant answer.
Maximum number of characters in a user prompt is 700.

Query examples

This section provides examples of some common queries, including typical user prompts and corresponding DataPrime queries.

Simple field-based filter
- User prompt: Show me all logs with application name default
- DataPrime query:

source logs
| filter $l.applicationname == 'default'

Multiple filters
- User prompt: Show me all logs with severity error or higher where the subsystem name is archive
- DataPrime query:

source logs
| filter $m.severity >= ERROR 
| filter $l.subsystemname == 'archive'

Aggregation
- User prompt: Count all errors by application name
- DataPrime query:

source logs 
| filter $m.severity == ERROR 
| groupby $l.applicationname aggregate count() as error_count

Aggregation and filtering
- User prompt: Show me all logs where the cloud provider is aws and group it by subsystem
- DataPrime query:

source logs 
| filter $d.resource.attributes['cloud.provider'] == 'aws' 
| groupby $l.subsystemname

Advanced calculation
- User prompt: Find the average grpc.timems where grpc code is not ok
- DataPrime query:

source logs 
| filter $d.grpc.code != 'ok' 
| groupby true aggregate avg($d.grpc.timems) as average_grpc_times

Note

Due to the DataPrime limitations, aggregate functions, such as sum, avg, count, etc., require a computation anchor to operate. As a result, the groupby true aggregate expression is used as a boolean value, serving as an anchor for the aggregate function.

Using the AI Query Assistant

STEP 1 . On the Logs Explore screen, select DataPrime as your query language.

STEP 2. Click on Query Assistant to enable it.

STEP 3. Enter your prompt in plain English. Click the Generate DataPrime Query button, or press Enter.

STEP 4. Review your prompt (the text in purple) and the resulting DataPrime query. If needed, you can modify the query in the DataPrime editor. Then, click the Run button to execute the query.

Give us your feedback

The more you use our AI Query Assistant, the better it becomes. While interacting with it, give its response a thumbs up or a thumbs down. If you think something needs correction or improvement, do let us know. Click the Thumbs Up or Thumbs Down button to make yourself heard.

If you like the generated query, give us a positive response (Thumbs Up) to show us that we’re on the right track.
If you choose to give a negative response (Thumbs Down), fill out the feedback form, specifying what you didn’t like, and send us your reply. You can make multiple selections and/or forward your suggestions as a free text.

Frequently asked questions

This section includes a series of questions commonly asked by customers. The questions cover such topics as the AI Query Assistant usage, compliance, data processing, privacy, etc.

Does the AI Query Assistant send data to a 3rd party LLM service?

Yes, the data is sent to OpenAI.

Does OpenAI use the data for training?

OpenAI does not use the data for training. For details, see the OpenAI guidelines.

Which data is sent to OpenAI?

With every user prompt, the AI Query Assistant sends customer fields with value examples in a prompt during query generation.

Is any of the AI Query Assistant data stored externally?

No data is stored permanently on an external platform. For operational and security reasons, such as abuse prevention, OpenAI may retain the data for up to 30 days. For details, see OpenAI guidelines.

How is hallucination risk managed and mitigated within the AI Query Assistant?

We use a DataPrime validator to verify the validity of each DataPrime query. Any invalid DataPrime query is rejected.

Has the AI Query Assistant been audited or assessed for bias, toxicity, political polarity, insult, threat, profanity or possible errors?

We use an internal mechanism to validate and monitor these issues and do not allow them to pass. We only return valid DataPrime queries, and any other subject is rejected.

Is the AI Query Assistant GDPR compliant?

Yes, we use OpenAI, which complies with GDPR requirements. In addition, Coralogix and OpenAI signed a data processing agreement (DPA) with updated SCCs. Coralogix has added OpenAI as an authorized sub-processor in case customers leak personal data into prompts. However, Coralogix does not have control over customers’ data input. Coralogix has checked OpenAI’s compliance with GDPR and thoroughly verified technical and organizational measures taken to ensure its compliance.

Is the AI Query Assistant HIPAA compliant?

No, we use OpenAI, which is not explicitly stated to be compliant with the Health Insurance Portability and Accountability Act (HIPAA) requirements. Customers must avoid processing Protected Health Information (PHI) through the Query Assistant and refrain from opting in if this is the case. Customers can also disable the use of the Query Assistant to prevent any PHI exposure.

Where is the OpenAI instance that processes the AI Query Assistant data located?

The AI Query Assistant uses OpenAI instances hosted by US-located Microsoft Azure data centers. For details, see the OpenAI Security Portal documentation.

Support

Need help?

Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.

Feel free to reach out to us via our in-app chat or by sending us an email to [email protected].

Dynamic Blocking

Next DataPrime Expression Language (DPXL)