edgehog

edgehog copied to clipboard

feat(push_rollout): `max_in_progress_updates` update api

1

provide an api for updating push_rollout. for now, only the field `max_in_progress_updates` is exposed through the graphql mutation. includes edits to `push_rollout_executor` to handle the updates. closes #278 re-implementation of...

noaccOS

feat(update_campaign_executor): handle update campaign updates

1

depends on #305 obviously

noaccOS

Right now we only support IPBase, which has some limitations. We should explore adding support for MapBox.

rbino

It should be possible to collect logs from remote devices and to display them. This feature should deal with different services and containers producing logs, rather than mixing all them...

bettio

Allow displaying remote device network status. For each network interface following information should be available: - interface name - addresses (IPv4 and IPv6 addresses) Displaying IP routes (IPv4 and IPv6)...

bettio

As an evolution over #307, it would be useful allowing remote network configuration. As a general idea it should be possible to decide whether an interface is configured with dhcp,...

bettio

Allow scaling Edgehog backend horizontally by using the native Elixir clustering mechanism

rbino

We should use Edgehog as a testbench for [OpenTelemetry](https://opentelemetry.io/docs/instrumentation/erlang/). This would integrate with the existing Prometheus metrics to provide additional functionalities, like function tracing (see [this blogpost](https://fly.io/phoenix-files/opentelemetry-and-the-infamous-n-plus-1/) for an example).

rbino

szakhlypa

Edgehog should have either integrated native support for Azure Blob Storage in addition to S3 APIs, or there should be a documented procedure about how to use it.

bettio