to create a new field you can use mutate add_field. but, from where you are getting "403/1/1". hoping 403 from dn and what about 1/1 ? end part of dn or static ?
Your example isn't valid JSON but perhaps you have simplified it.
Does the imdata always contain an array with a single element like in this case?
If yes, use a grok filter to parse the [imdata][0][l1PhysIf][attributes][dn] field and extract the interesting pieces. You can then use add_field in the same grok filter or in a separate mutate filter to piece together the different field values that you're picking up from different parts of the string.
in this scenario as magnus mentioned you need to choose grok patterns to extract node number and eth port of "dn" field. (Assuming imdata array has only 1 dn field)
I have run a few more API queries and yes it imdata only has 1 dn field in it.
I will test your filter and see how we can port them into elasticsearch. This will give us very good information on interface stats and hopefully we can build good visualizations for our monitoring.
Thanks for that @magnusbaeck I assumed that was automatically done from the Logstash side rather than from Kibana. The other mistake I made was I specified "text" while the correct one should be
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.