<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.foji.io/index.php?action=history&amp;feed=atom&amp;title=Logs_in_Explore</id>
	<title>Logs in Explore - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://docs.foji.io/index.php?action=history&amp;feed=atom&amp;title=Logs_in_Explore"/>
	<link rel="alternate" type="text/html" href="https://docs.foji.io/index.php?title=Logs_in_Explore&amp;action=history"/>
	<updated>2026-06-22T05:42:40Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.40.1</generator>
	<entry>
		<id>https://docs.foji.io/index.php?title=Logs_in_Explore&amp;diff=562&amp;oldid=prev</id>
		<title>Chris.Hansen: Created page with &quot;Along with metrics, Explore allows you to investigate your logs.  During an infrastructure monitoring and incident response, you can dig deeper into the metrics and logs to find the cause. Explore also allows you to correlate metrics and logs by viewing them side-by-side. This creates anew debugging workflow:  # Receive an alert. # Drill down and examine metrics. # Drill down again and search logs related to the metric and time interval (and in the future, distributed tr...&quot;</title>
		<link rel="alternate" type="text/html" href="https://docs.foji.io/index.php?title=Logs_in_Explore&amp;diff=562&amp;oldid=prev"/>
		<updated>2024-01-03T16:08:51Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Along with metrics, Explore allows you to investigate your logs.  During an infrastructure monitoring and incident response, you can dig deeper into the metrics and logs to find the cause. Explore also allows you to correlate metrics and logs by viewing them side-by-side. This creates anew debugging workflow:  # Receive an alert. # Drill down and examine metrics. # Drill down again and search logs related to the metric and time interval (and in the future, distributed tr...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Along with metrics, Explore allows you to investigate your logs.&lt;br /&gt;
&lt;br /&gt;
During an infrastructure monitoring and incident response, you can dig deeper into the metrics and logs to find the cause. Explore also allows you to correlate metrics and logs by viewing them side-by-side. This creates anew debugging workflow:&lt;br /&gt;
&lt;br /&gt;
# Receive an alert.&lt;br /&gt;
# Drill down and examine metrics.&lt;br /&gt;
# Drill down again and search logs related to the metric and time interval (and in the future, distributed traces).&lt;br /&gt;
&lt;br /&gt;
== Logs visualization ==&lt;br /&gt;
Results of log queries are shown as histograms in the graph and individual logs are explained in the following sections.&lt;br /&gt;
&lt;br /&gt;
FojiSoft supports a full range log volume histogram, the graph with log distribution for all entered log queries is shown automatically.&lt;br /&gt;
&lt;br /&gt;
=== Log level ===&lt;br /&gt;
For logs where a level label is specified, we use the value of the label to determine the log level and update color accordingly. If the log doesn’t have a level label specified, we try to find out if its content matches any of the supported expressions (see below for more information). The log level is always determined by the first match. In case FojiSoft is not able to determine a log level, it will be visualized with an unknown log level.&lt;br /&gt;
&lt;br /&gt;
Supported log levels and mapping of log level abbreviation and expressions:&lt;br /&gt;
&lt;br /&gt;
‍Supported expressions         Log level         Color&lt;br /&gt;
&lt;br /&gt;
emerg                                     critical            purple&lt;br /&gt;
&lt;br /&gt;
fatal                                        critical            purple&lt;br /&gt;
&lt;br /&gt;
alert                                        critical            purple&lt;br /&gt;
&lt;br /&gt;
crit                                          critical            purple&lt;br /&gt;
&lt;br /&gt;
critical                                    critical            purple&lt;br /&gt;
&lt;br /&gt;
err                                          error                red&lt;br /&gt;
&lt;br /&gt;
eror                                        error                red&lt;br /&gt;
&lt;br /&gt;
error                                       error                red&lt;br /&gt;
&lt;br /&gt;
warn                                      warning          yellow&lt;br /&gt;
&lt;br /&gt;
warning                                 warning          yellow&lt;br /&gt;
&lt;br /&gt;
info                                        info                 green&lt;br /&gt;
&lt;br /&gt;
information                           info                 green&lt;br /&gt;
&lt;br /&gt;
notice                                    info                 green&lt;br /&gt;
&lt;br /&gt;
dbug                                     debug             blue&lt;br /&gt;
&lt;br /&gt;
debug                                   debug             blue&lt;br /&gt;
&lt;br /&gt;
trace                                     trace               light blue&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;*&amp;lt;/nowiki&amp;gt;                                            unknown        grey&lt;br /&gt;
&lt;br /&gt;
=== Logs navigation ===&lt;br /&gt;
Logs navigation next to the log lines can be used to request more logs. You can do this by clicking on Older logs button on the bottom of navigation. This is especially useful when you hit the line limit and you want to see more logs. Each request that is run from the navigation is then displayed in the navigation as separate page. Every page is showing from and to timestamp of the incoming log lines. You can see previous results by clicking on the page. Explore is caching last five requests run from the logs navigation, so you are not re-running the same queries when clicking on the pages.&lt;br /&gt;
[[File:Visualize logs in explore navigation.png|center|frameless|600x600px]]&lt;br /&gt;
&lt;br /&gt;
=== Visualization options ===&lt;br /&gt;
You can customize how logs are displayed and select which columns are shown.&lt;br /&gt;
&lt;br /&gt;
==== Time ====&lt;br /&gt;
Shows or hides the time column. This is the timestamp associated with the log line as reported from the data source.&lt;br /&gt;
&lt;br /&gt;
==== Unique labels ====&lt;br /&gt;
Shows or hides the unique labels column that includes only non-common labels. All common labels are displayed above.&lt;br /&gt;
&lt;br /&gt;
==== Wrap lines ====&lt;br /&gt;
Set this to True if you want the display to use line wrapping. If set to False, it will result in horizontal scrolling.&lt;br /&gt;
&lt;br /&gt;
==== Prettify JSON ====&lt;br /&gt;
Set this to true to pretty print all JSON logs. This setting does not affect logs in any format other than JSON.&lt;br /&gt;
&lt;br /&gt;
==== Deduping ====&lt;br /&gt;
Log data can be very repetitive and Explore can help by hiding duplicate log lines. There are a few different deduplication algorithms that you can use:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Exact&amp;#039;&amp;#039;&amp;#039; - Exact matches are done on the whole line except for date fields.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Numbers&amp;#039;&amp;#039;&amp;#039; - Matches on the line after stripping out numbers such as durations, IP addresses, and so on.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Signature&amp;#039;&amp;#039;&amp;#039; - The most aggressive deduping, this strips all letters and numbers and matches on the remaining whitespace and punctuation.&lt;br /&gt;
&lt;br /&gt;
==== Flip results order ====&lt;br /&gt;
You can change the order of received logs from the default descending order (newest first) to ascending order (oldest first).&lt;br /&gt;
&lt;br /&gt;
=== Labels and detected fields ===&lt;br /&gt;
Each log row has an extendable area with its labels and detected fields, for more robust interaction. For all labels we have added the ability to filter for (positive filter) and filter out (negative filter) selected labels. Each field or labe lalso has a stats icon to display ad-hoc statistics in relation to all displayed logs.&lt;br /&gt;
&lt;br /&gt;
=== Escaping newlines ===&lt;br /&gt;
Explore automatically detects some incorrectly escaped sequences in log lines, such as new lines (\n, \r) or tabs (\t). When it detects such sequences, Explore provides an “Escape newlines” option.&lt;br /&gt;
&lt;br /&gt;
To automatically fix incorrectly escaped sequences that Explore has detected:&lt;br /&gt;
&lt;br /&gt;
# Click “Escape newlines” to replace the sequences.&lt;br /&gt;
# Manually review the replacements to confirm their correctness.&lt;br /&gt;
&lt;br /&gt;
Explore replaces these sequences. When it does so, the option will change from “Escape new lines” to “Remove escaping”. Evaluate the changes as the parsing may not be accurate based on the input received. You can revert the replacements by clicking “Remove escaping”.&lt;br /&gt;
&lt;br /&gt;
=== Derived fields links ===&lt;br /&gt;
By using Derived fields, you can turn any part of a log message into an internal or external link. The created link is visible as a button next to the Detected field in the Log details view.&lt;br /&gt;
[[File:Visualize logs in explore derived fields.png|center|frameless|600x600px]]&lt;br /&gt;
&lt;br /&gt;
=== Toggle detected fields ===&lt;br /&gt;
Expand a log line and then click the eye icon to show or hide fields.&lt;br /&gt;
[[File:Visualize logs in explore detected fields.gif|center|frameless|600x600px]]&lt;br /&gt;
&lt;br /&gt;
=== Specific features ===&lt;br /&gt;
FojiSoft does not index the contents of the logs, but rather a set of labels for each log stream. The logs from Foji are queried in a similar way to querying with label selectors in metrics. It uses labels to group log streams which can be made to match up with your metric labels.&lt;br /&gt;
&lt;br /&gt;
=== Switch from metrics to logs ===&lt;br /&gt;
If you switch from a metric query to a logs query (you can do a split first to have your metrics and logs side by side) then it will keep the labels from your query that exist in the logs and use those to query the log streams.&lt;br /&gt;
&lt;br /&gt;
This will return a chunk of logs in the selected time range that can be grepped/textsearched.&lt;br /&gt;
&lt;br /&gt;
== Live tailing ==&lt;br /&gt;
Use the Live tailing feature to see real-time logs on supported data sources.&lt;br /&gt;
&lt;br /&gt;
Click the Live button in the Explore toolbar to switch to Live tail view.&lt;br /&gt;
[[File:Visualize logs in explore live tailing.png|center|frameless|510x510px]]&lt;br /&gt;
While in Live tail view new logs will come from the bottom of the screen and will have fading contrasting background so you can keep track of what is new. Click the Pause button or scroll the logs view to pause the Live tailing and explore previous logs without interruption. Click Resume button to resume the Live tailing or click Stop button to exit Live tailing and go back to standard Explore view.&lt;br /&gt;
[[Category:Visualize]]&lt;/div&gt;</summary>
		<author><name>Chris.Hansen</name></author>
	</entry>
</feed>