mapper_parsing_exception in version 7.10.1

[dkupper76]

mapper_parsing_exception in version 7.10.1

[dkupper76]

Looks like it was a spacing or format error in the file, either that, or rebooting resolved that. However, even though the CDRs are showing up on the Logstash server, and there are no errors that I can see on the Logstash or Elasticsearch server, I am still not getting the CDRs to show up in Kibana or Elastic. Kibana does not have the index available, so I think I am past this initial issue, hopefully I can figure out the next issue, but I am going to close this as I got past the first issue reported, and if I can't get past the next issue, I will open another issue against this.

[damhau]

It's great to know that somebody is using this.
I created this for a customer several years ago and I haven't worked on it since but let me know if I can help.
If I find some time I'll try to make it work for newer version of ELK and build a docker image.

I'll look at the issue every week, feel free to open a new one if needed.

[dkupper76]

Awesome, I appreciate your reply and possible making of a newer version and Docker image.

Just to update you, I am now one step closer to getting this all working, I finally am getting data to go from Logstash to Elasticsearch and showing up in Kibana. In the Learn Logstash section of the elastic website, I found that I needed to run two commands (which are probably very basic for setting up Logstash, but for a newbie to ELK Stack and trying to setup something very quickly, can be overlooked). The commands I am referring to are:

bin/logstash -f first-pipeline.conf --config.test_and_exit

bin/logstash -f first-pipeline.conf --config.reload.automatic

Except I had to use ./logstash -f cucm.conf --config.test_and_exit as I was in the bin directory and I was using the files you provided, though I had to make some modficiations to them, including combining the cucm.conf and elasticsearch.conf into a single .conf file.

Now I am trying to get the visualizations working, but I am seeing the following error:

“There is a problem with this saved object
The saved search associated with this object no longer exists.
If you know what this error means, go ahead and fix it — otherwise click the delete button above.”

The saved search it is referring to is: “search_0” with an ID of: "CUCM-All-Call"

Do you have any idea of what parameters the search was specifying? Was it something like: “cdrRecordType.keyword” or was it something else?

Again I appreciate your help, and if need be, I can open a new issue, but for now, I am trying to figure it out.

Thank you,

Daryl