Manage Search and Queries
Manage searches and queries by creating reusable components instead of rewriting the same queries repeatedly. Build macros for common patterns, search templates for parameterized searches, search packages to organize investigations, and lists to filter results.
Macros
Macros are uniquely named shortcuts for longer search queries. They make searches easier to create and reuse by eliminating the need to repeatedly type complex query strings. You can use macros to build new search queries and include them in Search, Dashboards, Reports, Alert Rules, Label Packages, Search Packages, and Search Templates. When you type a macro name in the Search field, Logpoint automatically expands it into the full query.
Macros can be combined with other macros or with custom search expressions, and you can create as many macros as required. When you update a macro, the change is automatically applied everywhere the macro is used, allowing you to maintain and refine queries from a single location.
Macro Examples
Search Templates
Search Template stores search queries with placeholders. The stored queries are called base queries. The placeholders in the base queries are used as variables, which you can replace with actual search keywords during runtime. You can save multiple base queries in a search template and use them to search queries or create dashboard widgets. The search templates retain the last visualization applied to the widgets. You can drill-down on the search results from the non-edit mode of the widget of the search templates.
My Search Templates contains all the search templates you have created or cloned. The vendor search templates are grouped under Vendor Search Templates and those shared by other users are grouped under Shared Search Templates.
Sharing Search Templates
Sharing search templates enables teams to collaborate on the same set of standardized searches. Make a template available to other users and control their access by assigning read, edit, or full permissions. Updates to a shared search template are automatically reflected for everyone who has access, ensuring consistency across investigations.
Each parameter in a shared search template is categorized into three types:
Global parameters can be changed only by users with Edit or Full permissions. Changes in the global parameters are reflected for all users using the shared search template. The following parameters are global:
The name, description, queries, and field values of the search template.
Title and order of tabs, including tab creation and deletion.
Title, query, dimensions, and positions of widgets, including widget addition and deletion.
Personalized parameters can be changed by all users. However, the changes to the personalized parameters apply only to the users who made them. The following parameters are personalized:
The updateable parameters
Selected repos
Time range
Hybrid parameters can be changed by all users. If the user changing the parameters has the Edit or Full permissions, the changes are reflected for all the users. However, if the user has only the Read permission, the changes are reflected only for the user making the change. The following parameters are hybrid:
Chart types of widgets
Legends and legend labels of widgets
Trend state of widgets
Manage Search Templates
Search Packages
Search Packages are collections of saved searches that let you rerun the same searches without re-entering them. They group related searches so you can organize them logically and quickly run the required one.
There are three types of Search Packages:
My Packages Searches that you create and organize yourself. This is the default view.
Vendor Packages Integration-specific packages provided by Logpoint. You can’t edit these packages directly, but you can clone them and modify the clone. Modified clones appear under My Packages.
Shared Packages Packages shared between you and other users. These can include:
Packages you created and shared yourself
Vendor packages that you or another user cloned and modified
In addition to sharing packages with other Logpoint users or importing them into another Logpoint server or instance, you can share Search Packages with people in your organization through the Public API. This is useful when colleagues don’t have access to Logpoint.
Saved Searches
Saved Searches store individual search queries so you can reuse them later. Selecting a saved search automatically loads the query into the search bar and runs it, displaying the corresponding results.
Lists
Lists are collections of values that can be used as criteria in search query to filter search results. For example, you can search all logs generated from the Sales team by creating a list SALES_USER with a username of all sales members and using the query user in SALES_USER in Search.
Logpoint supports Static List and Dynamic List.
Static Lists
Static List is a collection of pre-defined values that doesn’t change unless you add or remove values from it.
For example, you can create a list IP_BLACKLIST and add all the blacklisted IPs in it. You can check logs for the blocked IP Address using the device_ip query in IP_BLACKLIST in Search.

To display the age limit or last updated columns, click MORE >> Columns and select Age Limit(in minutes) or Last Updated.
Dynamic List
Dynamic List stores the values that can be updated using the toList process command. For example, to list all the users in Logpoint, create a dynamic list USERS and execute the toList process command to add values in the List. To execute the process command to update the list values whenever new users log into the system.
Adding Values to a Dynamic List
The previously added list is initially empty. Use the toList process command to add field values from the search result into the list.
Syntax:
This process command takes two arguments: list name and field name. It prompts an error message if you provide more than two arguments or an incorrect list name.
Example:
The query above adds the device_ip values from the search results to the device_ip_list list.

If you execute the same process command with a different field name, it adds the values of the field to the existing list.
For example, if you execute the query device_ip=* | process toList(device_ip_list, device_ip), then execute device_ip=* | process toList(device_ip_list, device_name), device_name is added in the list device_ip_list.
Data Expiry in Dynamic List
In a dynamic list with an Age Limit, each item inherits the list’s expiry time. For example, if the list’s expiry time is set to 3 hours, any item added to the list will automatically expire after 3 hours. If an item is updated, its expiry time resets, and the item will expire 3 hours after the last update.
In contrast, a list without an Age Limit considers all items as permanent, giving them an expiry time of 0. To delete these items, you must set an Age Limit for the list and then update the item. Once the item exceeds the new expiry time, it will be removed.
Importing / Exporting a List
To export a list, select the list and click EXPORT.
Last updated
Was this helpful?


