Custom Log Source Name

[cask]

Hello all,

I am creating a custom log source for a host. Im seeing (no log data available) for this source but I can verify that there are files on this source. Here is the current path, I have followed instructions from documentation
D:\Advisor\logs\autopilot\2024\6\Auto-Pilot_2024-6-#-#-#-#.txt (No log data available)

This is what our logs look like. Could anyone help me with this issue, and explain where I'm going wrong? 

Thank you!

[AntonPineiro]

Hi,

I do not know if you are using log monitoring classic or Grail but this is done in two steps normally:

1. Autodiscovery (you can create a custom log source if log is not autodiscovered for an important process).
2. Ingestion rule.

Have you create a log ingestion rule?

Best regards

[GerardJ · Accepted solution]

Hi
As Anton said you should set up an ingest rule
have you looked at security rules ? https://docs.dynatrace.com/docs/shortlink/log-monitoring-custom-source#security-rules
as from my understanding your log file path or filename do not match this rule :

Hope this helps

Regards

[Manupriya1]

Hi @Gert  , 

I also tried ingesting from a log source called E:\TSCL_Runtime\TSCLUSERS\SYSTEM\JOURNALS\log\PROD*.txt (No  log data available) but didn't get any log data . the only catch here is that i have placed some log files here in this folder as a POC to check if we can actually see the logs from this location or not . Apparently DT one agent is able to read the location but not the logs inside .  Any help here !!

[AntonPineiro]

Hi,

Which ingestion rule have you created to ingest that log?

Best regards

[Manupriya1]

is there any other way or please guide if I am doing something wrong here 

[Manupriya1]

I have updated the ingestion rules as : E:\TSCL_Runtime\TSCLUSERS\SYSTEM\JOURNALS\log\Jobs\PROD*.txt . Still no response