Customer needs to define a custom log source that is not been detected

[miguelocem]

Hi a Customer and I we're trying to set up a custom log source in Dynatrace to ingest logs from files with a .iqmsg extension. Here's what we've done so far:

• Created a custom log source in Dynatrace.
• Defined a log processing rule that should capture logs from any path where .iqmsg files appear.
• Verified that the .iqmsg files are being written and updated on the file system.
• The rule is configured to match any path containing .iqmsg files.

However, in the Dynatrace UI, we keep seeing the message:
"No log data available"

We’ve double-checked the file permissions and confirmed that the OneAgent has access to the directory.

Questions:

1. Is there a specific format or requirement for .iqmsg files to be recognized as valid log sources?
2. Are there any known limitations or additional configuration steps needed for custom log sources in Dynatrace?
3. Could the issue be related to how the rule is defined (e.g., path matching syntax)?
4. Is there a way to debug or trace what Dynatrace is doing with the custom log source?

Any help or guidance would be appreciated!

[g_kat · Accepted solution]

Hi @miguelocem ,

It's been some time since I worked with Log Ingestion, but back then in order to get some non-standard log files ingested I had to override the Log Security Rules:

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

Basically, OA accepts by default specific types of logs and you need to define any other types you want in addition to the Custom Log Source and Log Processing rules.

Hope it helps.

George

[miguelocem]

Thanks a lot!