# Unable to parse pipe separated data in nifi logs using logstash(This data is being generated due to a Controller Status Reporting Task)

**URL:** <https://discuss.elastic.co/t/unable-to-parse-pipe-separated-data-in-nifi-logs-using-logstash-this-data-is-being-generated-due-to-a-controller-status-reporting-task/159507>\
**Category:** Logstash\
**Created:** [December 5, 2018, 10:19am UTC](https://discuss.elastic.co/t/unable-to-parse-pipe-separated-data-in-nifi-logs-using-logstash-this-data-is-being-generated-due-to-a-controller-status-reporting-task/159507 "2018-12-05T10:19:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PoonamMishra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/poonammishra/32/38465_2.png) [@PoonamMishra](https://discuss.elastic.co/u/PoonamMishra)\
**Post date:** [December 5, 2018, 10:19am UTC](https://discuss.elastic.co/t/unable-to-parse-pipe-separated-data-in-nifi-logs-using-logstash-this-data-is-being-generated-due-to-a-controller-status-reporting-task/159507/1 "2018-12-05T10:19:42Z")

</div>

Below is the sample log that is being generated due to Controller Status Reporting Task.

## 2018-12-05 10:06:38,061 INFO [Timer-Driven Process Thread-12] o.a.n.c.C.Connections Connection Statuses:

## | Connection ID | Source | Connection Name | Destination | Flow Files In | Flow Files Out | FlowFiles Queued |

| 45c4XXXX-d9b2-XXXc-d168-XXXb9104816e | EvaluateJsonPath | matched | FailOverIngestionXXX | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 11 / 6.43 KB (+0/+0 bytes) |  
| 4aab324f-b795-1c42-775b-3148a9253ef4 | putElasticsearchHttp | failure | putElasticsearchHttp | 50 / 38.23 KB (+0/+0 bytes) | 50 / 38.23 KB (+0/+0 bytes) | 5 / 3.82 KB (+0/+0 bytes) |  
| 01661003-be2e-118a-b3f5-4fc0f00cda72 | FailOverIngestionPort\_v0.1 | | FailOverIngestionPort\_v0.1 | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |  
| dcd03f5c-c141-1dce-a426-d4a4420996ba | ingestionPort\_v0.2\_PE | | ingestionPort\_v0.2\_PE | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |  
| 5d1d2e03-0166-1000-0998-20698b061837 | ingestionPort\_v0.2 | | ingestionPort\_v0.2 | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |  
| 98951cbb-3ced-1cb0-6e73-2749124ee2d3 | provenanceMonitoring | | LogAttribute | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |  
| dcd04081-c141-1dce-1edd-1ea0954f92d2 | ingestionPort\_v0.2\_PE | | ingestionPort\_v0.2\_PE | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |  
| 7349e222-0167-1000-4972-8df929be36d4 | fetchDataFromHive | success | successFetchDataFromHive | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) | 0 / 0 bytes (+0/+0 bytes) |

My expected output is two have an index with attributes as per the header of the above data:  
eg: {  
"Connection ID":["45c4XXXX-d9b2-XXXc-d168-XXXb9104816e "],  
"Source":["EvaluateJsonPath"],  
"Connection Name": ["matched"].  
"Destination":["FailOverIngestionXXX"],  
"Flow Files In":["0 / 0 bytes (+0/+0 bytes)"],  
"Flow Files Out":["0 / 0 bytes (+0/+0 bytes)"],  
"FlowFiles Queued":["11 / 6.43 KB (+0/+0 bytes)"]  
}

PS: I am fairly a beginner to #logstash

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 2, 2019, 10:19am UTC](https://discuss.elastic.co/t/unable-to-parse-pipe-separated-data-in-nifi-logs-using-logstash-this-data-is-being-generated-due-to-a-controller-status-reporting-task/159507/2 "2019-01-02T10:19:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.