- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Haven't had this issue, but there should be multiple ways to fix it ![]()
Think the easiest would be to make another filelog config. That force log insight to look at both locations
Fx.
[filelog|IIS_Drive_C]
; IMPORTANT: Change the directory as per the environment
directory=C:\inetpub\logs\LogFiles\W3SVC2\
include=*.log
event_marker=^\d{4}-\d{2}-\d{2}
tags={"ms_product":"iis"}
parser=iisLogParser
[filelog|IIS_Drive_D]
; IMPORTANT: Change the directory as per the environment
directory=D:\Windows\System32\LogFiles\1\W3SVC2
include=*.log
event_marker=^\d{4}-\d{2}-\d{2}
tags={"ms_product":"iis"}
parser=iisLogParser
If this does not work for you. You can create another agent group, but with a different name and directory config.
Hope this helps
Blogging at https://MichaelRyom.dk