gravwell/datastore repository overview

⁠Gravwell Datastore

The Gravwell Datastore component is used to synchronize state across multiple Gravwell webservers when running in a distributed frontend mode.

The Datastore allows for rapid scale up and scale down of webservers in a high load environment with many users. The datastore requires persistent storage and acts as the master control node when when more than one webserver is in use.

⁠Configuration

For full configuration details, see the Datastore Documentation⁠ for full configuration details.

Additional information on distributed webservers and Gravwell high availability see the Gravwell Distributed Setup⁠ docs.

⁠Datastore Configuration

The Datastore component shares the same gravwell.conf file as the indexer and webserver components so that it CAN be run co-located with a webserver. In a fully distributed setup, it needs its own gravwell.conf located in /opt/gravwell/etc/.

The following is an minimal example of a gravwell.conf:

[global]
# You should set this to whatever the frontends use
Control-Auth=ControlSecrets

# These defaults should be fine
Datastore-Log-Location=/opt/gravwell/log
Datastore-User-DB-Path=/opt/gravwell/etc/datastore-users.db
Datastore-Resource-Store=/opt/gravwell/resources/datastore
Datastore-Web-Store-Path=/opt/gravwell/etc/datastore-webstore.db

# These are optional parameters; the datastore will listen on 0.0.0.0:9405 by default.
#Datastore-Listen-Address=10.0.0.5    # listen only on 10.0.0.5
#Datastore-Port=9555                    # listen on port 9555 instead of 9405

⁠Docker configuration Parameters

The Docker deployment enables some feature configuration and control using environment variables. Each Gravwell docker component ships with the Crash Reporting Service⁠ which can be disabled using environment variables.

⁠Free Edition

Free community licenses for Gravwell are available⁠.