Table of Contents | ||||
---|---|---|---|---|
|
Overview
You can find events containing specific values across all the data tables in their current domain using the Global search option in the data search area.
...
What permissions do I need to perform a global search?
In order to access this area to perform a global search (Data Search → Explore Your Data → Global Search tab), you need to have a role with the management level of the Global Searches searchespermission. If you do not have this permission, you will not be able to see the tab and hence perform any global search.
Be aware that this permission requires to have management permissions on Finders to be activated.
...
Take into account that you need to activate any level of the parent permission (Finders)to enable the permission checkbox (know more about permissions here).
...
Note |
---|
Domain feature Note that this feature is only enabled in certain domains by default so even though you have the required permissions, you might still be unable to see it. If you need to use it and is not enabled in your domain, contact the Devo support team. |
Using the global search
...
the
...
global search
...
Rw ui steps macro | |||||||||
---|---|---|---|---|---|---|---|---|---|
Go to Data search and select the Global search tab.
Enter the expression you want to search for. You can use standard AND and OR operators, use an asterisk ( * ) as a wildcard, or quotation marks ( "" ) to indicate exact expressions. For example: user1@domain.comORuser2@domain.comAND"illegal access"AND*apache
Click to open the time menu and select the time period over which you want to search (see the section below for more info).
Select the tables that you wish to search. Note that, by default, all tables are selected, and switching off one of them will switch off the Select all tables option.
Hit the
|
...
Note |
---|
Activity shown In order to avoid long loading times, note that the global search only returns events from data tables that had some activity for the last 7 days. Due to this, you may miss some data in your global search results. |
Anchor | ||||
---|---|---|---|---|
|
...
Rw ui tabs macro | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
You can set a time interval following the steps described in the picture below.
You can also introduce time ranges manually using date language expressions, which gives you more flexibility and precision when searching your data. Simply click on the date field and write the desired time expression or edit the existing one. The field turns red and an explanatory message appears until a valid date is entered. Click Apply when you finish. When the and the expressions will be translated into the corresponding dates.
You can use a mix of both absolute and date language expressions in any given time range (for example, the to date can be relative and the from date absolute, and vice versa). For date language expressions, the current moment "now()" is used as the reference point. OperatorsYou can establish absolute dates in the required format:
With date language expressions, use a series of mathematical operations to move away from the current time which is used as the reference point. You can use multiple operators at once and the execution order is from left to right:
Time expressionsLet's suppose the current time (which we refer to as "now()") is Sunday, 05 February 2017, 13:37:05. The table below shows the resulting time when different expressions are applied. Note that this isn't an exhaustive list:
|
...
You can find the following fields with the following information in the table:
eventdate | The date and time in which Devo received the event. |
---|---|
technology | The first and highest tag level. It indicates the type of technology from which the data comes. |
brand | The second tag level. It indicates the vendor of the aforementioned technology. |
phylum | The third tag level and the first optional, also known as type. It describes and categorizes the data source inside the company. |
family | The fourth tag level and the second optional, also known as subtype 1. It further describes and categorizes the data source in case subdivisions are necessary. |
genus | The fifth tag level and the third optional, also known as subtype 2. If further describes and categorizes the data source in case more subdivisions are necessary. |
species | The sixth and lowest tag level and the fourth optional, also known as subtype 3. It further describes and categorizes the data source in case even more subdivisions are necessary. |
tables | The tables in which the token appears. |
hostName | The name of the machine from which the event originated. |
hostIp | The IP address of the machine from which the event originated. |
message | The data received in the event. |
Info |
---|
Metadata from other tables Be aware that sometimes the tags from the fields do not coincide with the tables in which the token appears. This is because those tables extract information and metadata from the ones in which they actually appear. |
...