OpenSearch Dashboards Best Practices
After setting up your Logz.io's Log Management account, it's time to learn how to gain more out of your logs.
Once you've sent your data to Logz.io, you can search and query your logs to debug, troubleshoot, and monitor issues as quickly and effectively as possible.
Logs support a few query methods, including:
Lucene / OpenSearch Dashboards Query Language (DQL)
The default query language in Logz.io is Lucene, and you can use it or DQL syntax to query your logs. However, it’s recommended to use Lucene while it enables using your query in an alert or optimizer.
You can search for free text by typing the text string you want to find; for example, error will return all words containing this string, and using quotation marks, "error", will return only the specific word you're searching for.
You can also use the exists query with the relevant value. For example:
_exists_:error.
To search for a value in a specific field, use the following syntax:
status:200
Use the boolean operators AND, OR, and NOT to create more complex searches. For example, to search for a specific status that doesn't contain a certain word:
status:406 NOT "error"
If you want to perform range-related searches, the fields must be mapped as numbers (long, float, double, etc.). Then, you can use the following syntax to find all status codes between 400-499:
status:[400 TO 499]
To make your search more complex, you can find status codes 400-499 with the extension php:
status:[400 TO 499] AND extension:PHP
Or, find status codes 400-499 with the extension php or html:
status:[400 TO 499] AND (extension:php OR extension:html)
Apply regex to search
Using Regex can overload your system and cause performance issues in your account. If Regex is necessary, it's best to apply filters and use shorter timeframes.
Logz.io uses Apache Lucene's regular expression engine to parse regex queries, supporting regexp and query_string.
While Lucene's regex supports all Unicode characters, several characters are reserved as operators and cannot be searched on their own:
. ? + * | { } [ ] ( ) " \
Depending on the optional operators enabled, some additional characters may also be reserved. These characters are:
# @ & < > ~
However, you can still use reserved characters by applying a backslash or double-quotes. For example:
\* will render as a * sign.
\# will render as a # sign.
\() will render as brackets.
To use Regex in a search query in OpenSearch, you'll need to use the following template:
fieldName:/.*value.*/.
For example, you have a field called sentence that holds the following line: "The quick brown fox jumps over the lazy dog".
To find one of the values in the field, such as fox, you'll need to use the following query:
sentence:/.*fox.*/.
Search and filter your logs
Learn how to search and filter your log data with Logz.io.
Enrich log results
You can add additional columns to your logs field view.
Find the field you'd like to add, hover over it and click on the + button.
Once the field is added, you can move or remove it using its inner menu.
Finally, you can save your search and its view by clicking on the Save option, at the top navigation bar.
Filter log results
To narrow down your search, click the Add filter option underneath the search bar.
Choose the field, operator, and value you'd like to apply in your filter, and click save. You can also create a custom label to rename the filter for better identification.
Once you've set your filter, clicking on it will open additional abilities such as pinning it across all apps, excluding results, temporarily disabling it, editing, or deleting it.
Select logs' time frame
The default period to display results is 15 minutes. You can edit this time frame by clicking on the Show dates link or clicking on the calendar icon.
The calendar icon offers popular time frames for you to choose from and lets you select the refresh rate of your data.
The Show dates option lets you set a start and end time. In the popup, select between the following options:
- Relative - Set a start and end date to view your data
- Now - Get real-time troubleshooting and monitoring of your logs
- Absolute - Browse the calendar view and choose any time frame to view your data. In this option, you can type the time frame you want to view
Create Log Visualizations
Not sure what to visualize? If your logs haven't been parsed into fields yet, our support team can assist with prasing your logs and extracting the fields needed to create your visualizations.
In the following video, you'll be able to see how to create a visualization dashboard based on your logs:
Divide your log data
You can divide logs from different environments by type, by utilizing Logz.io's sub accounts option.
Create a sub account and configure it to receive the same logs as an existing account, mapping it as a different data type.
For example, if a metadata field is assigned as an Object in your production environment, you can assign it as a String in your testing environment by creating a sub account to which you’ll send the same logs.
You can also send data from each environment to a dedicated sub account to monitor them individually.
Learn more about creating and managing sub accounts and about field mapping in your account.