Logs Not captured

[juveria]

Hi Team,

We are enabling log monitoring for one server in PreProd
Customer has given us the path  :  E:\NRI_Logs\HSL_NRI\ DT\15092025 .log
We have added the rules in custom log source and log ingest rules but still unable to capture the logs
Link to the environment :  https://fso.hdfcsec.com/e/92ce50fc-1436-494f-9d53-eb71b403a520/ui/settings/HOST-D6832D53ADBDE067/bu

…Can u please help what could be missing so that i can capture the logs.

Thanks in advance

[juveria]

https://dynatrace.slack.com/archives/C74N5RMK6/p1758619203169829
Added support archive here 

[Mohamed_Hamdy]

Hi @juveria 

i can see there is a space before DT and before .log, is it added like this?

Best Regards,

Hamdy

[juveria]

No Hamdy, E:\NRI_Logs\HSL_NRI\DT\*.log,

I have added in attachment snap.

Regards,

Juveria

[Mohamed_Hamdy]

thank you @juveria , Apologies—I hadn’t checked the attached snapshot.
Unfortunately, I don’t have access to the support archive or the tenant. I believe you’ll need to follow the rules for adding a custom log file: the log path must be located on the first or second level of the log or logs directory. For more details, please see: https://docs.dynatrace.com/managed/shortlink/log-monitoring-custom-source#security-rules

[juveria]

Thanks Hamdy will try that.

[Akhil-Jayendran]

Hi @juveria ,

As Hamdy mentioned, you should add a custom log source in order to get the logs in Dynatrace. @Mohamed_Hamdy  

Does Dynatrace really have a limitation on the log path? I couldn’t find it in the documentation. I noticed this restriction applies to autodiscovery, not to custom log sources. Once we add the log source, we should be able to ingest the logs without issues.

https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-log-ingestion-vi...

[juveria]

Hi Akhil, 

Yes its already added in custom log source, but regarding the path i just checked for other applications we can see the path is not a concern , even for the log output on the fourth level we are capturing the logs

Regards,

[Mohamed_Hamdy]

Hello @Akhil-Jayendran , There are a few rules that must be met. One of them is: “A log path must be located on the first or second level of the log or logs directory.” However, I believe the first rule (log extension separated by ., -, or _) is already satisfied.
References:
https://docs.dynatrace.com/managed/analyze-explore-automate/log-monitoring/acquire-log-data/log-cust...

https://docs.dynatrace.com/docs/analyze-explore-automate/log-monitoring/acquire-log-data/log-custom-...

@juveria, could you please share a screenshot of the files under this directory?

[juveria]

Hi Hamdy,

PFA