Skip to content

Commit 0271687

Browse files
authored
Merge pull request #7303 from Brenduns/14015489-fix-tunnel-logging
Unraveling bad revert
2 parents 660d51a + 60c48e2 commit 0271687

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

memdocs/intune/protect/microsoft-tunnel-monitor.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,12 +141,12 @@ For more information and command-line examples, see [mst-cli command-line tool f
141141

142142
## View Microsoft Tunnel logs
143143

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:
145145

146146
- **ocserv** - Display server logs.
147147
- **mstunnel-agent**: Display agent logs.
148148
- **mstunnel_monitor**: Display monitoring task logs.
149-
149+
150150
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`.
151151

152152
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`.
@@ -157,6 +157,7 @@ More options for *journalctl*:
157157
- `man journalctl` – Display additional information.
158158
- `man journalctl.conf` Display information on configuration
159159
For more information about *journalctl*, see the documentation for the version of Linux that you use.
160+
<!-- Pending ocserv-access -->
160161

161162
## Next steps
162163

0 commit comments

Comments
 (0)