# Sampling\_rate
**URL:** https://discuss.elastic.co/t/sampling-rate/153544
**Category:** Beats
**Tags:** filebeat
**Created:** [October 23, 2018, 8:26am UTC](https://discuss.elastic.co/t/sampling-rate/153544 "2018-10-23T08:26:35Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@merceskoba](https://discuss.elastic.co/u/merceskoba)
#### Post date: [October 23, 2018, 8:26am UTC](https://discuss.elastic.co/t/sampling-rate/153544/1 "2018-10-23T08:26:36Z")
Hello dear,
Is there `sampling_rate` in filebeat service ?
For example,
`sampling_rate: 0.1`, it means 0.1 is 10/100 or 10%. So, filebeat will send the logs only 10% of logs.
sampling\_rate or sampling\_filter maybe...
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [October 23, 2018, 11:00am UTC](https://discuss.elastic.co/t/sampling-rate/153544/2 "2018-10-23T11:00:59Z")
Sampling is not supported by beats yet.
---
### Author:  [@merceskoba](https://discuss.elastic.co/u/merceskoba)
#### Post date: [October 23, 2018, 11:34am UTC](https://discuss.elastic.co/t/sampling-rate/153544/3 "2018-10-23T11:34:25Z")
Thank you very much for your confirmation.
Will it be implemented in the future maybe ? 🙂
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [October 24, 2018, 5:40pm UTC](https://discuss.elastic.co/t/sampling-rate/153544/4 "2018-10-24T17:40:50Z")
We're thinking about adding QoS, rate limiting, and sampling. Even in conjunction with defining groups, group hierarchies, and conditionals, so to allow you to configure actions (e.g. more aggressive filtering) on soft and hard limits.
Some experimental code here (I'm not yet satisfied by it, though): [https://github.com/elastic/beats/pull/7082](https://github.com/elastic/beats/pull/7082)
---
### Author:  [@GuiBacon](https://discuss.elastic.co/u/GuiBacon)
#### Post date: [October 24, 2018, 6:01pm UTC](https://discuss.elastic.co/t/sampling-rate/153544/5 "2018-10-24T18:01:41Z")
What is interesting is that, how your old system was able to perform good using this cursed DAQ Assistant. If you want to program NI hardware properly, do not use DAQ Assistant! It initializes and releases HW at every iteration! Use proper DAQmx functions! Create/start task BEFORE the loop, and only stop it AFTER! You should have only the "DAQmx Read.vi" function inside the loop.
[turnkey pcb](https://www.7pcb.ca/)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 21, 2018, 6:07pm UTC](https://discuss.elastic.co/t/sampling-rate/153544/6 "2018-11-21T18:07:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.