Successfully read and parse metrics asynchronously. The metrics are then ingested into a InfluxDB server.
To run this you need to have a local InfluxDB server running. Works needs to be done on creating a container environment where all of this is handled automatically. But until then you can run:
docker run -p 8086:8086 -v myInfluxVolume:/var/lib/influxdb2 influxdb:latest
and set up the server manually before running the simulation.
Things that still need to be done:
Error handling
Reading API key from some secret location
Create/configure InfluxDB container
Parameterize all the things (we probably want to read the dataset directory from a config/env file or something similar)
Closes #3 #2 #6 #17 #18
Also has effects on #15 since we use InfluxDB for the implementation.
The structure of the Go code probably needs to be reorganized into a single module. We seem to have misunderstood how to organize a Go project. This is pretty easily fixed though.
Successfully read and parse metrics asynchronously. The metrics are then ingested into a InfluxDB server.
To run this you need to have a local InfluxDB server running. Works needs to be done on creating a container environment where all of this is handled automatically. But until then you can run:
docker run -p 8086:8086 -v myInfluxVolume:/var/lib/influxdb2 influxdb:latest
and set up the server manually before running the simulation.Things that still need to be done:
Closes #3 #2 #6 #17 #18 Also has effects on #15 since we use InfluxDB for the implementation.