Jun 12 2018
07:32 AM
- last edited on
Apr 07 2022
05:11 PM
by
TechCommunityAP
Jun 12 2018
07:32 AM
- last edited on
Apr 07 2022
05:11 PM
by
TechCommunityAP
When ingesting data into OMS via a Custom Log source, is there anyway to identify the log file path the data was collected from? For example, if a single '_CL' table was populated from many log file paths, is the log file path for each log entry made available anywhere? Or would the user have to explicitly log the file path for that to be made available?
I have not seen any metadata for Custom Log entries that includes log file path, so I'm pretty sure the answer is 'no', or you have to log it yourself, but just wanted to double check.
Thank you!
Jun 14 2018 08:49 AM
Hey Brandon,
Indeed it seems there is no such capability. I will keep checking in case it's supported and hidden, and update if so.
Jun 17 2018 03:32 AM
Hey,
So indeed that is not supported. To push for implementation, you can ask for it through our User Voice and other users can vote for it too.
Thanks,
Noa