# Importing CSV data via metricbeat **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [September 10, 2018, 7:44am UTC](https://discuss.elastic.co/t/importing-csv-data-via-metricbeat/147913 "2018-09-10T07:44:58Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![sribalaji\_dac](https://avatars.discourse-cdn.com/v4/letter/s/8dc957/32.png) [@sribalaji\_dac](https://discuss.elastic.co/u/sribalaji_dac)\ **Post date:** [September 10, 2018, 10:05am UTC](https://discuss.elastic.co/t/importing-csv-data-via-metricbeat/147913/3 "2018-09-10T10:05:47Z")
Thanks @Mario_Castro for the reply. is there any workaround to achieve the same ? I could see some article about using logstash csv filter plugin. But to use that, i need to write a custom code/script which does the expected behavior in the following order (with all the extra/additional hops) script(api call) -\> csv log \> logstash csvplugin \> logstash \> elasticsearch To use this approach, we would end up in maintaining the script for failures/cron... > [@Monitoring LDAP server](https://discuss.elastic.co/t/monitoring-ldap-server/130653/4): > > Franco, Either of these methods of indexing is fine. Which is preferable is probably most dependent on personal preference/situational criteria. The method of indexing, though, doesn't really affect the ability to subsequently use queries to extract the information you describe. That's all up to the mapping/document structure you choose. Best, Glen --- _[View the full topic](https://discuss.elastic.co/t/importing-csv-data-via-metricbeat/147913)._