Skip to content
GitLab

Draft: 820 - Oasislink from local to central as TCP server

Open Daniel Lehmberg requested to merge 820_separate_logstash_tcpserver into develop

Relates to issues #820 and #886 This merge request follows up the closed merge requests !697 (closed), !727 (closed) and !784 (closed).

Here the Oasis link is implemented in a separate component to the Nomad app - a TCP Server. In particular the runs on a local Oasis installation and receives logs on the same address and port than where logstash logs are sent on the central unit.

For local installations it can therefore be interpreted as a logstash proxy. Unless running a logstash instance itself, all logs are submitted to the central Oasis where the logs are then eventually stored in logstash.

Open questions:

  • To identify a local Oasis we read the IP address on the FastAPI receiving end. Do we still need to adapt the field deployment_id per local instance (we would make sure that this is unique -- maybe taking a hash from some config parameters)?

To clarify:

  • A problem for testing is currently, that when the app is started with nomad app run app, then there the logs are different set than to the log config in docker. Should this maybe be fixed? (If starting Nomad with nomad app run app, then no API calls are processed in logstash format).
Edited by Daniel Lehmberg