This tutorial will guide you on your first steps with Coralogix and help you start enjoying reduced time to detect and solve production problems.
Coralogix supports many integrations which we divide into 6 main categories:
Coralogix provides support for all its integrations and an integration session with our engineers can be booked directly here.
Coralogix allows data parsing using Regex to perform the following operations:
Coralogix “Streama” engine allows it to analyze all data on the fly without the usage of storage, the TCO optimizer enables users to define the use case per app/sub/severity and define policies for optimized data routing. We typically see 70% cost reduction by this feature, and our support team is available 24/7 to assist in defining the correct policies and also policy exceptions.
Coralogix enables data enrichment on the fly to make logs smarter/more readable. There are 3 types of enrichments:
The first place to see your logs after they have been parsed and enriched, is the Coralogix live tail. Live tail is a low latency, pre index/storage stream of logs, it sends logs directly from the Coralogix queue to your client and allows data filtering by app/sub, or any “grep” command or sequence. It also allows you to choose which specific log fields will be displayed and enables you to “prettify” JSON data or view it as raw text. Live tail is available in the Coralogix interface, or via CLI.
Both unstructured and JSON-structured log queries are supported:
Returns logs containing Your login was unauthorized OR Wrong password. Login unauthorized.
Returns logs containing the phrase your exact match string
Returns logs that match url:/some/url.php or url:/some/url.html
Returns logs that exactly match url:/some/url.php
Returns logs where value of statusCode key is between 200 and 399
In order to make data investigations simpler, and help you find that needle in the haystack, Coralogix created a proprietary real-time clustering algorithm that automatically identifies logs of the same type/origin and clusters them into a log template. This enables turning hours of data, and millions of records into a short list of data templates with easy visualization options and added value such as template normal behavior learning or the ability to zoom into specific templates. Loggregation does not require any pre-defining and works on all data types. To make Loggregation most accurate, have your main log message as a root key and not nested (typically “log”, “message”, “msg”, “text” etc) No need to do anything for unstructured logs. Learn more here.
Alerts in Coralogix can be defined directly from your query by clicking on the “Create Alert” button or from the “Alert” interface at the top bar of the Coralogix screen. Coralogix has 6 main and 12 secondary alert types:
Coralogix harnesses all its features, alerts, queries, anomalies, Loggregation templates, Normal behavior learning, New & Suspected error detection, and custom widgets, to enable a next generation experience for CICD acceleration. By using the Coralogix “Tags” feature, you can plug your CICD platform into Coralogix, and send your build logs, metrics, and most of all – Version tags. Coralogix will then compare versions uploaded to the same service in 2 different points in time, and provide an automated benchmark of the key quality metrics for new version release, enabling you to add your own widgets for version over version comparison of any trend or SLA you would like to visualize. Learn more about Version Tags here.
To enter Kibana you need to login to Coralogix first (see How to login chapter) and then click on Kibana button in the top right corner.
You will see the Kibana main screen:
On the left side you can see shortcuts to:
Discover enables you to quickly search and filter your data, and get information about the structure of the fields.
As you can see in the attached screenshot:
Below the search bar there is a “+Add filter” button. Use it for easier filtering. Details about the feature: https://www.elastic.co/guide/en/kibana/6.8/field-filter.html
As you can see as an example coralogix.metadata.applicationName and log fields were added as display filters. To add a new display filter click on the add button next to the field which is on the left at Available fields column. To remove a display filter click on the remove button next to the field which is on the left of in the Selected fields.
Even though Kibana doesn’t have the Coralogix left filter for Applications/Subsystems, you may limit your search to logs from a specific application and subsystem by applying the following filters to your search on kibana search bar:
This guide is the very basic getting started guide to get you up to speed and help you extract the initial value from the product. To learn more about Coralogix, visit our Help Center or the full Tutorials page .You are always welcome to Schedule a 1:1 demo and we’ll walk you through step by step.