# Possible asgraphite limitations?
**URL:** https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944
**Category:** Tools
**Created:** [February 13, 2018, 8:32pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944 "2018-02-13T20:32:17Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@ra.centro](https://discuss.aerospike.com/u/ra.centro)
#### Post date: [February 13, 2018, 8:32pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944/1 "2018-02-13T20:32:17Z")
We using asgraphite to push metrics, however we recently discovered our asgraphite polling interval did not match our graphite storage schema. I’ve been playing with the --interval option, however it seems to break when set to anything less than the default of 300s. Has anyone else run into this problem or is there a limitation of asgraphite we’re just not aware of?
Regards,
---
### Author:  [@kporter](https://discuss.aerospike.com/u/kporter)
#### Post date: [February 13, 2018, 11:00pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944/2 "2018-02-13T23:00:30Z")
How does it break?
---
### Author:  [@ra.centro](https://discuss.aerospike.com/u/ra.centro)
#### Post date: [February 14, 2018, 2:18pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944/3 "2018-02-14T14:18:35Z")
Fair question, I should have elaborated. When “–interval 60” is set in the init options and the service restarted, we get an initial single push of metrics then nothing. If I remove the “–interval” option and restart the service, metrics get pushed on the default 300s interval as stated in asgraphite’s code.
---
### Author:  [@kporter](https://discuss.aerospike.com/u/kporter)
#### Post date: [February 14, 2018, 10:55pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944/4 "2018-02-14T22:55:21Z")
The default for interval appears to be 30s:
>
Is asgraphite printing any errors?
---
### Author:  [@ra.centro](https://discuss.aerospike.com/u/ra.centro)
#### Post date: [February 15, 2018, 2:23pm UTC](https://discuss.aerospike.com/t/possible-asgraphite-limitations/4944/5 "2018-02-15T14:23:43Z")
That’s odd, the version we have in production has default=300. However, that being said. I found that the assignment of INTERVAL\_POLL\_DATA was being classed as a string and breaking at line 591 time.sleep(INTERVAL\_POLL\_DATA).
I added a float() around the variable assignment and all seems good now. I’ll take a look at what’s on github to see if we just need to pull the latest build. Perhaps we’re just behind the times and this was fixed.