A golang ETL to collect, filter and output logs/events.
More information of the graph backend and how it is modeled, can be found here
The current development is aiming to implement a Neo4j-backed inventory ProofOfConcept.
It will use the information fetched from the inputs of qwatch
and derived inventory information out of it.
-
0.7.0.x implement basic Neo4j backend
-
0.7.1.x implement deriving inventory from
docker-events
input- Images
- Containers
- network configuration
-
0.7.2.x create
docker-api
input- Fetch and push engine
Info()
- fetch and push
swarm.Node
- fetch and push
ContainerList
#22 - fetch and push
ImageList
#23 - fetch and push
NetworkList
#24 - fetch and push
VolumeList
#25 - fetch and push
ServiceList
#26 - fetch and push
TasksList
#27
- Fetch and push engine
-
0.8 Optimising
- Create Indices
- Use bloom filter?
- Extract Neo4j inventory logic to qnib/qinventory
-
implement deriving inventory from
docker-logs
input (does it make sense)- which processes are running inside
- how are the files doing
- fetch and push
SecretList
#28 - fetch and push
PluginList
#29 - fetch and push
CheckpointList
#30