I'm setting up an instance of this on IMaRS servers to hopefully solve #26. Two ways to do this:
airflow ts_ingest pushes data from IMaRS server to influxDB on FWC google cloud
airflow ts_ingest pushes data from IMaRS server to influxDB at IMaRS. Then grafana running on FWC google cloud connects to IMaRS influxDB.
Either is fine. 1 is easier so I will do that. It is probably more performant too. But this did give me an idea:
perhaps ts_ingest should push data to a list of endpoints? That should be an easy feature addition and could be useful. For example: in the future we may want to push this same data from IMaRS into the FWC and FKNMS dashboards. This will require either:
two airflow tasks. ie ts_ingest_fwc and ts_ingest_fknms with some duplication in filepaths
ts_ingest tasks organized based on our data structures that push to multiple influxdb endpoints
I'm setting up an instance of this on IMaRS servers to hopefully solve #26. Two ways to do this:
ts_ingest
pushes data from IMaRS server to influxDB on FWC google cloudts_ingest
pushes data from IMaRS server to influxDB at IMaRS. Then grafana running on FWC google cloud connects to IMaRS influxDB.Either is fine. 1 is easier so I will do that. It is probably more performant too. But this did give me an idea:
perhaps ts_ingest should push data to a list of endpoints? That should be an easy feature addition and could be useful. For example: in the future we may want to push this same data from IMaRS into the FWC and FKNMS dashboards. This will require either:
ts_ingest_fwc
andts_ingest_fknms
with some duplication in filepathsts_ingest
tasks organized based on our data structures that push to multiple influxdb endpoints