# Save request results in a new elastic index or a new database **URL:** \ **Category:** Elasticsearch\ **Created:** [July 11, 2017, 9:33am UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616 "2017-07-11T09:33:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![AitZaid](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@AitZaid](https://discuss.elastic.co/u/AitZaid)\ **Post date:** [July 11, 2017, 9:33am UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/1 "2017-07-11T09:33:30Z")
Hi, I'm quite new with elasticsearch and kibana and I wonder if there is a way to save the data used to make the graphs with kibana in a new index, or even in an outside database, and then make the data processing of the saved data. Because the way I understood it Kibana to make a graph aggregate data from all the logs in elasticsearch so when we activate auto-refresh every 2 minutes to have real time graph it re aggregate all the log it's in elasticsearch, so what I'm trying to accomplish is to take the last 2 minutes logs add it to my database and making the processe on this database so i won't overload my elasticsearch. thank you for your help 🙂 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 11, 2017, 9:38am UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/2 "2017-07-11T09:38:24Z")
There's not at this stage sorry! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [July 11, 2017, 9:54am UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/3 "2017-07-11T09:54:34Z")
> I won't overload my elasticsearch Did you overload it yet? I mean a lot of OS and ES cache is involved and it should be ok OOTB. Are you sure you need something like this? ---
**Author:** ![AitZaid](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@AitZaid](https://discuss.elastic.co/u/AitZaid)\ **Post date:** [July 11, 2017, 1:18pm UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/4 "2017-07-11T13:18:56Z")
Well, not yet, but I feel that if I keep reconsidering every log in my elasticsearch each time I make an update to my graph it might happen sooner or later? but maybe I'm wrong like I said i'm new with ELK . but to give you a more precise explanation of my probleme here is an example: I have a bar graph that shows http requests, and group them as either a successful request or failed ones: and the thing is we have like 30 request now and in 2 minutes 5 new ones will be added, and still we reconsider all 35 logs instead of adding the 5 new in the graph ![](https://us1.discourse-cdn.com/elastic/original/3X/f/4/f4f28e6f3f2bfb3503e46285a8333d485a108f03.png) thank you ; ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [July 11, 2017, 1:38pm UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/5 "2017-07-11T13:38:32Z")
> I have a bar graph that shows http requests, and group them as either a successful request or failed ones: and the thing is we have like 30 request now and in 2 minutes 5 new ones will be added, and still we reconsider all 35 logs instead of adding the 5 new in the graph Yes. But I don't think it's a problem IMO. Specifically for time based indices which are append-only indices. Which means that segments, specifically the older ones are cached by the OS for a long time. And also with instant aggregations some cache on ES level makes that even faster. (You need to upgrade though). In short, I'd say: "don't try to fix an issue that you don't have". ---
**Author:** ![AitZaid](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@AitZaid](https://discuss.elastic.co/u/AitZaid)\ **Post date:** [July 11, 2017, 2:00pm UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/6 "2017-07-11T14:00:35Z")
ok, So I worry for nothing 🙂 , by the way as for the upgrade we are currently woking on upgrading to kibana 5 🙂 . thank you for your implication and responsiveness . ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 8, 2017, 2:00pm UTC](https://discuss.elastic.co/t/save-request-results-in-a-new-elastic-index-or-a-new-database/92616/7 "2017-08-08T14:00:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.