You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/intune/protect/microsoft-tunnel-monitor.md
+5-22Lines changed: 5 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ keywords:
5
5
author: brenduns
6
6
ms.author: brenduns
7
7
manager: dougeby
8
-
ms.date: 04/11/2022
8
+
ms.date: 08/23/2021
9
9
ms.topic: how-to
10
10
ms.service: microsoft-intune
11
11
ms.subservice: protect
@@ -141,32 +141,15 @@ For more information and command-line examples, see [mst-cli command-line tool f
141
141
142
142
## View Microsoft Tunnel logs
143
143
144
-
Microsoft Tunnel logs information to the Linux server logs in the *syslog* format. To view log entries, use the **journalctl -t** command followed by one or more tags that are specific to Microsoft Tunnel entries
144
+
Microsoft Tunnel logs information to the Linux server logs in the *syslog* format. To view log entries, use the **journalctl -t** command followed by one or more tags that are specific to Microsoft Tunnel entries:
By default, access logging is disabled. Enabling access logs can reduce performance, depending on the number of active connections and usage patterns on the server. Logging for DNS connections increases the verbosity of the logs, which can become noisy.
152
-
153
-
Access logs have the following format: `<Server timestamp><Server Name><ProcessID on Server><userId><deviceId><protocol><src IP and port><dst IP and port><bytes sent><bytes received><connection time in seconds>` For example:
2. set TRACE_SESSIONS=2 to include logging for DNS connections
161
-
3. Run `mst-cli server restart` to restart the server.
162
-
163
-
If access logs are too noisy, you can turn off DNS connection logging by setting TRACE_SESSIONS=1 and restarting the server.
164
149
165
-
Command line examples for *journalctl*:
150
+
For example, to view information for only the tunnel server, run `journalctl -t ocserv`. To view information for all three, you can run `journalctl -t ocserv -t mstunnel-agent -t mstunnel_monitor`.
166
151
167
-
- To view information for only the tunnel server, run `journalctl -t ocserv`.
168
-
- To view information for all log options, you can run `journalctl -t ocserv -t ocserv-access -t mstunnel-agent -t mstunnel_monitor`.
169
-
- Add `-f` to the command to display an active and continuing view of the log file. For example, to actively monitor ongoing processes for Microsoft Tunnel, run `journalctl -t mstunnel_monitor -f`.
152
+
You can add `-f` to the command to display an active and continuing view of the log file. For example, to actively monitor ongoing processes for Microsoft Tunnel, run `journalctl -t mstunnel_monitor -f`.
0 commit comments