# Beat Metrics to Redis **URL:** \ **Category:** Beats\ **Created:** [January 4, 2017, 6:13pm UTC](https://discuss.elastic.co/t/beat-metrics-to-redis/70590 "2017-01-04T18:13:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Jeferson\_Martins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeferson_martins/32/5849_2.png) [@Jeferson\_Martins](https://discuss.elastic.co/u/Jeferson_Martins)\ **Post date:** [January 4, 2017, 6:13pm UTC](https://discuss.elastic.co/t/beat-metrics-to-redis/70590/1 "2017-01-04T18:13:22Z")
Hi, We have to get the number of events from FileBeat that are generated after read action and save the result in Redis. We used the logging.metrics.enabled configuration but this only output the statistics in FileBeat output or logfile, being necessary read this new file with Filebeat. How can I send this information to Redis without read a Filebeat output from File? ---
**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\ **Post date:** [January 4, 2017, 7:24pm UTC](https://discuss.elastic.co/t/beat-metrics-to-redis/70590/2 "2017-01-04T19:24:13Z")
There's no really better option at the moment. The statistics can also be exported via an http interface if you start filebeat with something like `-httpprof :5000` then accessing `http://localhost:5000/debug/vars`. However, this HTTP endpoint can also be used for enabling Filebeat profiling, so we don't recommend using this method in production. We do plan to have a way to get these metrics into Elasticsearch. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 25, 2017, 6:13pm UTC](https://discuss.elastic.co/t/beat-metrics-to-redis/70590/3 "2017-01-25T18:13:34Z")
This topic was automatically closed after 21 days. New replies are no longer allowed.