3 ms·

Hi HN, I built this thing! The idea came a few years back when me and an angel investor in the company I had founded were involved in a BI project, defining and

by rlonn 8y ago

Hi HN, I built this thing! The idea came a few years back when me and an angel investor in the company I had founded were involved in a BI project, defining and collecting some basic KPIs for the business. At one point when we were thinking about where to store the very limited set of time series data that was our complete set of KPI metrics, the investor said “why isn’t there some service where you can just send a few numeric data points for storage, and get them back, without a lot of hassle?”. I really liked it as I saw it as a very simple idea, easy to implement but which still felt like it may be new/unique. The new thing here, of course, is not the ability to store time series data. The new/unique thing is the low barrier to entry. The API is extremely small and simple to use and learn, and there is no registration required to start using the service. I tried to make onboarding as frictionless as possible, and I think it’s hard to make it simpler than it is now. All feedback is greatly appreciated! Some perhaps useful links: Site: https://pushdata.io https://pushdata.io API docs: https://speca.io/ragnarlonn/pushdata-io https://speca.io/ragnarlonn/pushdata-io Blog article about making pushdata.io: https://bit.ly/2RGuIxc https://bit.ly/2RGuIxc

gravypod 8y ago
It might be a good idea to add more RESTful handling of ingestion. Something similar to the following POST /{account}/{series} [ { metrics: { "a": 10, "b": 20, "c": [1, 2, 3, 4] }, occurred: "2018-01-01 01:01:01" }, { metrics: { "a": 20, "b": 30, "c": [2, 3, 4, 5] }, occurred: "2018-01-01 01:01:02" } ] The overhead of an HTTP call of every data point submission might now work well in low bandwith situations. Also in cases where you have intermittent internet connections supplying a timestamp for when an event happens is helpful.
- rlonn 8y ago
  There is an /api/timeseries end point where you can POST multiple data points with one single call. while putting that end point under /{email}/{series} may be more intuitive, I wanted to make it obvious that it is separate, as that end point is a premium feature. See https://speca.io/ragnarlonn/pushdata-io#extended-api https://speca.io/ragnarlonn/pushdata-io#extended-api

by rlonn 8y ago

gravypod 8y ago

It might be a good idea to add more RESTful handling of ingestion. Something similar to the following POST /{account}/{series} [ { metrics: { "a": 10, "b": 20, "c": [1, 2, 3, 4] }, occurred: "2018-01-01 01:01:01" }, { metrics: { "a": 20, "b": 30, "c": [2, 3, 4, 5] }, occurred: "2018-01-01 01:01:02" } ] The overhead of an HTTP call of every data point submission might now work well in low bandwith situations. Also in cases where you have intermittent internet connections supplying a timestamp for when an event happens is helpful.

rlonn 8y ago
There is an /api/timeseries end point where you can POST multiple data points with one single call. while putting that end point under /{email}/{series} may be more intuitive, I wanted to make it obvious that it is separate, as that end point is a premium feature. See https://speca.io/ragnarlonn/pushdata-io#extended-api https://speca.io/ragnarlonn/pushdata-io#extended-api