# How to extract a message JSON value using JSON Input under Kibana Visualization **URL:** \ **Category:** Kibana\ **Created:** [May 21, 2020, 7:32am UTC](https://discuss.elastic.co/t/how-to-extract-a-message-json-value-using-json-input-under-kibana-visualization/233690 "2020-05-21T07:32:02Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![lukeelmers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukeelmers/32/35230_2.png) [@lukeelmers](https://discuss.elastic.co/u/lukeelmers)\ **Post date:** [May 25, 2020, 3:36pm UTC](https://discuss.elastic.co/t/how-to-extract-a-message-json-value-using-json-input-under-kibana-visualization/233690/4 "2020-05-25T15:36:34Z")
> Just wanted to know if Json Input can be similar to scripted fields so that the fields are only created/generated at visualization time. This is correct, you can use the JSON input to add a scripted field "on the fly" to your visualization. You can find an example of this in my comment here: > [@Kibana JSON Input Question](https://discuss.elastic.co/t/kibana-json-input-question/232895/2): > > Hi there, All that really happens with JSON inputs is that the JSON gets included along with the rest of the aggregation generated by the editor and sent to Elasticsearch. The [docs on aggregations](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations.html) explain the options for these in more detail, but we most commonly see folks using them to include inline scripts to run against the selected field, e.g. { "script": { "inline": "doc['name'].value ...whatever", "lang": "painless" } } The important thing to keep in mind is that these scri… --- _[View the full topic](https://discuss.elastic.co/t/how-to-extract-a-message-json-value-using-json-input-under-kibana-visualization/233690)._