quick-docs/modules/ROOT/pages/_partials/proc_log-files-GUI.adoc

[id='using-gnome-logs-to-view-log-files']
= Using Gnome Logs to view log files

To view log files in GUI, use the `GNOME Logs` application. `GNOME Logs` is not installed by default. 
   
* Install Via GUI :

** Press the `Super` key 
** Type `Software`
** In the `Search` field type `Logs` and choose the `GNOME Logs` item from the list of results 
** Install the application

* Install Via Command Line :

----
$ sudo dnf install gnome-Logs
----

In `GNOME Logs`, you can filter for time periods, search within logs, and display categories.

* To select a log file type, from the side bar of GNOME Logs, select the type to view.
* To select a time period, from the menu bar, click `*Logs*`, and select a time period.
* To search within logs, select a log file from the results pane.
. Click the search icon.
. Enter one or more search criterion in the search field.
Review "view logs on Fedora" quick-doc - Remove Caution - Review and Check View Log Information via Systemctl - Add Using journalctl to View Log Information for a Specific Service - Add to know more about systemd -> understanding-and-administering-systemd - Sections can be moved up one level replaceing rsyslog - Improve con_viewing-logs.adoc with adding some usefull information - Change in using nano and vim to you can use favourite text editor - Remove rsyslog completly - Add -b and --list-boots if the user needs flter log messages for the current boot or view old log's - instead of using bold for commands and file/folder names, maybe make them monospace too. That does'nt work in _NOTE_ - "Using the command line to open log files in a text editor" -> "Use a text editor" as a separate section. - Observe a Warning when editing view_log.adoc and there is a PR in ASCCIDOCTOR https://github.com/asciidoctor/asciidoctor/issues/2855. [Ticket: 107] - https://pagure.io/fedora-docs/quick-docs/issue/107 2019-03-28 12:17:36 +00:00			`[id='using-gnome-logs-to-view-log-files']`
			`= Using Gnome Logs to view log files`
Viewing logs (joflynn) 2018-07-10 14:49:26 +00:00
Review "view logs on Fedora" quick-doc - Remove Caution - Review and Check View Log Information via Systemctl - Add Using journalctl to View Log Information for a Specific Service - Add to know more about systemd -> understanding-and-administering-systemd - Sections can be moved up one level replaceing rsyslog - Improve con_viewing-logs.adoc with adding some usefull information - Change in using nano and vim to you can use favourite text editor - Remove rsyslog completly - Add -b and --list-boots if the user needs flter log messages for the current boot or view old log's - instead of using bold for commands and file/folder names, maybe make them monospace too. That does'nt work in _NOTE_ - "Using the command line to open log files in a text editor" -> "Use a text editor" as a separate section. - Observe a Warning when editing view_log.adoc and there is a PR in ASCCIDOCTOR https://github.com/asciidoctor/asciidoctor/issues/2855. [Ticket: 107] - https://pagure.io/fedora-docs/quick-docs/issue/107 2019-03-28 12:17:36 +00:00			To view log files in GUI, use the `GNOME Logs` application. `GNOME Logs` is not installed by default.

			`* Install Via GUI :`
Viewing logs (joflynn) 2018-07-10 14:49:26 +00:00
Review "view logs on Fedora" quick-doc - Remove Caution - Review and Check View Log Information via Systemctl - Add Using journalctl to View Log Information for a Specific Service - Add to know more about systemd -> understanding-and-administering-systemd - Sections can be moved up one level replaceing rsyslog - Improve con_viewing-logs.adoc with adding some usefull information - Change in using nano and vim to you can use favourite text editor - Remove rsyslog completly - Add -b and --list-boots if the user needs flter log messages for the current boot or view old log's - instead of using bold for commands and file/folder names, maybe make them monospace too. That does'nt work in _NOTE_ - "Using the command line to open log files in a text editor" -> "Use a text editor" as a separate section. - Observe a Warning when editing view_log.adoc and there is a PR in ASCCIDOCTOR https://github.com/asciidoctor/asciidoctor/issues/2855. [Ticket: 107] - https://pagure.io/fedora-docs/quick-docs/issue/107 2019-03-28 12:17:36 +00:00			** Press the `Super` key
			** Type `Software`
			** In the `Search` field type `Logs` and choose the `GNOME Logs` item from the list of results
			`** Install the application`

			`* Install Via Command Line :`

			`----`
			`$ sudo dnf install gnome-Logs`
			`----`
Viewing logs (joflynn) 2018-07-10 14:49:26 +00:00
			In `GNOME Logs`, you can filter for time periods, search within logs, and display categories.

			`* To select a log file type, from the side bar of GNOME Logs, select the type to view.`
Review "view logs on Fedora" quick-doc - Remove Caution - Review and Check View Log Information via Systemctl - Add Using journalctl to View Log Information for a Specific Service - Add to know more about systemd -> understanding-and-administering-systemd - Sections can be moved up one level replaceing rsyslog - Improve con_viewing-logs.adoc with adding some usefull information - Change in using nano and vim to you can use favourite text editor - Remove rsyslog completly - Add -b and --list-boots if the user needs flter log messages for the current boot or view old log's - instead of using bold for commands and file/folder names, maybe make them monospace too. That does'nt work in _NOTE_ - "Using the command line to open log files in a text editor" -> "Use a text editor" as a separate section. - Observe a Warning when editing view_log.adoc and there is a PR in ASCCIDOCTOR https://github.com/asciidoctor/asciidoctor/issues/2855. [Ticket: 107] - https://pagure.io/fedora-docs/quick-docs/issue/107 2019-03-28 12:17:36 +00:00			* To select a time period, from the menu bar, click `Logs`, and select a time period.
Viewing logs (joflynn) 2018-07-10 14:49:26 +00:00			`* To search within logs, select a log file from the results pane.`
			`. Click the search icon.`
			`. Enter one or more search criterion in the search field.`