Go to file
John Shahid 4a3a286f2e Check for valgrind and mercurial
If valgrind isn't found, `make valgrind` will be disabled. Otherwise it
will run valgrind to make sure the parser doesn't leak any memory. If
mercurial isn't found an error will be displayed and configure will
abort.

Close #978
2014-11-05 18:49:49 -05:00
.hooks add a pre-commit hook 2014-06-23 13:25:59 -04:00
_vendor/raft Don't try to take 2 snapshots at a time 2014-10-31 14:00:56 -04:00
admin Move admin assets into the compiled binary. 2014-10-20 17:43:42 -04:00
api Remove some nonsense 2014-10-30 14:16:46 -04:00
checkers Restructure the codebase to be more idiomatic 2014-06-30 11:31:08 -04:00
client Move the influxdb test to an examples directory 2014-10-27 17:57:22 -04:00
cluster Don't write points if they are too old 2014-11-03 17:28:47 -05:00
common Use the standard heap implementation 2014-10-21 17:57:13 -04:00
configuration Make the raft logging configurable 2014-10-30 16:03:13 -04:00
coordinator Don't try to close the protobuf server if it's not open 2014-11-05 16:46:54 -05:00
daemon Return an appropriate exit code if the daemon exists because of errors 2014-11-05 18:13:34 -05:00
datastore Don't write points if they are too old 2014-11-03 17:28:47 -05:00
docs Update docs for OS X. 2014-11-02 21:15:09 -05:00
engine Add some docs 2014-10-31 15:17:45 -04:00
integration Don't write points if they are too old 2014-11-03 17:28:47 -05:00
metastore cleanup the storage keys and point iteration in the shard's code 2014-09-10 14:08:07 -04:00
parser Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
protocol Merge points at the shard level 2014-10-21 17:57:13 -04:00
scripts Replaces sudo with su in init script 2014-11-05 16:32:14 -05:00
server Make sure all services are stopped properly 2014-11-05 18:14:56 -05:00
shared/admin Fix continuous query functionality in the api 2014-10-27 17:25:17 -04:00
statik Fix continuous query functionality in the api 2014-10-27 17:25:17 -04:00
tools fix a compilation error 2014-10-27 18:00:02 -04:00
utils/burn-in Script to randomly write batches of points over a time interval. 2014-03-14 10:16:30 -04:00
wal ensure close file before rename bookmark file. 2014-08-19 09:57:39 +08:00
.gitignore Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
.rvmrc Revert "Bump rvm to 2.1.0" 2014-01-30 16:58:46 -05:00
.travis.yml update travis email notification and go version 2014-11-05 17:21:27 -05:00
CHANGELOG.md Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
Gemfile prefer gemfile and rvm over manually setting up the env. 2013-11-04 15:51:57 -05:00
Gemfile.lock prefer gemfile and rvm over manually setting up the env. 2013-11-04 15:51:57 -05:00
LICENSE update the year in the LICENSE file 2014-05-20 15:34:20 -04:00
Makefile.in Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
README.md Add a contributing doc 2014-07-15 12:53:35 -04:00
cert.pem fix #190. Close #194 2014-01-28 14:58:56 -05:00
config.sample.toml don't enable raft debug log by default 2014-10-31 14:50:04 -04:00
configure Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
configure.ac Check for valgrind and mercurial 2014-11-05 18:49:49 -05:00
release.sh don't try to create another source package 2014-10-24 18:10:21 -04:00

README.md

InfluxDB Build Status

InfluxDB is an open source distributed time series database with no external dependencies. It's useful for recording metrics, events, and performing analytics.

It has a built-in HTTP API so you don't have to write any server side code to get up and running.

InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms.

Quickstart

Building

You don't need to build the project to use it. Pre-built binaries and instructions to install InfluxDB are here. That's the recommended way to get it running. However, if you want to contribute to the core of InfluxDB, you'll need to build. For those adventurous enough, you can follow along on our docs