Highlight Sets — Xshell

(?<!\w)(WARNING|CRITICAL)(?!\w) This ensures WARNING is highlighted only as a whole word, not inside UNWARNING . CPU usage: [9][0-9]%|CPU usage: 100% Matches "CPU usage: 95%" or "CPU usage: 100%". 4. Timestamps (ISO 8601) \d4-\d2-\d2T\d2:\d2:\d2 Great for making log timestamps stand out. 5. HTTP Status Codes \b(200|201|204|301|302|400|401|403|404|500|502|503)\b Color-code 200s in green, 500s in red. 6. SSH Login/Logout Events (Accepted|Failed) password for .* from Part 5: Managing Multiple Highlight Sets for Different Roles One size rarely fits all. Create multiple highlight sets and toggle them based on your task.

Native integration with SSH, Serial, TELNET, and RDP in one client, plus a GUI for managing highlight sets without editing JSON files. Part 10: Expert Tips & Hidden Gems Tip 1: Use Highlight Sets as a Crude Log Filter Create a rule with Text Color = Background Color (e.g., black-on-black) to effectively hide lines containing DEBUG or VERBOSE . Not a true filter, but works visually. Tip 2: Chain Highlight Sets with Actions (Advanced) In Xshell’s Quick Commands , you can trigger a highlight set change via script. Example: xshell highlight sets

Start small. Create a set with just two rules: one for errors (red) and one for successes (green). Gradually add patterns for IPs, timestamps, and domain-specific keywords. Export your set, share it with your team, and standardize your visual language across all sessions. Gradually add patterns for IPs