# Enterprise Search (App Search) - Using Kibana for engine's content analysis **URL:** \ **Category:** Elastic Search\ **Created:** [May 27, 2021, 9:21am UTC](https://discuss.elastic.co/t/enterprise-search-app-search-using-kibana-for-engines-content-analysis/274169 "2021-05-27T09:21:07Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ross.bell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ross.bell/32/77559_2.png) [@ross.bell](https://discuss.elastic.co/u/ross.bell)\ **Post date:** [May 27, 2021, 3:29pm UTC](https://discuss.elastic.co/t/enterprise-search-app-search-using-kibana-for-engines-content-analysis/274169/2 "2021-05-27T15:29:46Z")
Hey @SanderP, You're right, you can access the App Search indexes with an index pattern as mentioned here: [Elastic index name with enterprise app search engine names - #2 by JasonStoltz](https://discuss.elastic.co/t/elastic-index-name-with-enterprise-app-search-engine-names/273637/2). Definitely be sure not to modify any of the data in those indexes. Otherwise, the performance impact is pretty minimal assuming you're not querying against that data very frequently. It depends on your cluster size, but less frequently than once a minute should be negligible on _any_ cluster size. What field would you intend to use as the time field? Most documents should have a _created at_ field, and many should have _updated at_. You could also use a custom schema field contained in your document structure. Note that if you use system fields like the data used to track _created at_, there is no future guarantee that those fields will be preserved as they currently exist. Ross --- _[View the full topic](https://discuss.elastic.co/t/enterprise-search-app-search-using-kibana-for-engines-content-analysis/274169)._