topic Re: CSV Data in Log Analytics

Ingest CSV data to Dynatrace

anuj08_jain — Wed, 17 Dec 2025 13:56:01 GMT

Is their Any way we can ingest the CSV files in Dynatrace?

I have CSV file test.csv:

timestamp,host,process,pid,loglevel,message 2025-08-26 14:21:05,web01,sshd,32145,INFO,"Accepted password for custuser3 from 10.10.5.44 port 60233 ssh2" 2025-08-26 14:22:11,web01,sshd,32147,WARNING,"Failed password for custuser2 from 10.10.5.55 port 60291 ssh2" 2025-08-26 14:23:30,db01,mysqld,4521,INFO,"Connection established for user root@10.10.1.22" 2025-08-26 14:24:18,app01,java,2234,ERROR,"NullPointerException in com.example.service.OrderService" 2025-08-26 14:25:05,web02,nginx,1120,INFO,"200 GET /index.html from 10.10.3.11" 2025-08-26 14:26:47,web02,nginx,1120,ERROR,"502 Bad Gateway for /api/orders" 2025-08-26 14:27:12,db01,mysqld,4521,WARNING,"Slow query detected: SELECT * FROM orders" 2025-08-26 14:28:09,app02,python,8876,INFO,"Task scheduler executed job cleanup.py" 2025-08-26 14:29:40,app02,python,8876,ERROR,"ModuleNotFoundError: No module named 'requests'" 2025-08-26 14:30:25,web01,sshd,32149,INFO,"Accepted publickey for admin from 10.10.5.77 port 60312 ssh2"

Re: CSV Data

Julius_Loman — Wed, 27 Aug 2025 09:03:00 GMT

Certainly, you can do it (assuming log monitoring classic - in Dynatrace Managed based on your tag), using various methods. If OneAgent log ingestion (OneAgent ships the logs), then you need to define a custom log source and a log ingest rule. Additionally, log processing rules are required to parse the content into log attributes.

Re: CSV Data

anuj08_jain — Wed, 27 Aug 2025 09:32:46 GMT

So that means Dynatrace, doesn't parse csv data by it's own and we dont have any pre-defined Ingest Rule for the case?
Also Do we have any support to view this data similar like Splunk - lookup or inputlookup something like that?

Re: CSV Data

Julius_Loman — Wed, 27 Aug 2025 10:55:48 GMT

Custom log source - is to specify you have a custom log which is not automatically detected. CSV files generated by an application probably won't be autodetected - when you ingest the log by OneAgent.
Ingest rule - is to specify the log (or entries) have to be ingested by OneAgent.
Processing rule - is to parse the content into log attributes. You will see the log lines in the content attributes. You probably want this to map the CSV fields to log attributes in Dynatrace, such as log source or level.

Re: CSV Data

HansLougas — Thu, 28 Aug 2025 13:33:50 GMT

@anuj08_jain Please see documentation for lookup data, if you are using log on Grail: https://docs.dynatrace.com/docs/shortlink/grail-lookup-data