Not able to get metrics if started before Hasura

[timesy]

I am using the metric adapter in Kubernets and there it might start before Hasura is ready. In that case I get the following error:

thread 'main' panicked at 'no entry found for key', src/collectors/event_triggers.rs:122:20
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Some metrics are then not visible (e.g. hasura_successful_event_triggers), even after Hasura started. In Kubernetes I found no way to start the adapter after Hasura to mitigate this problem. When using HASURA_GRAPHQL_ENDPOINT with a domain and restarting the deployment it seems to work as it connects with the old Hasura instance before it starts the new one. However this is unreliable in case the pod crashes.

I am using Version 0.2.1 (can't use 0.3.0, as I don't have an OTel collector and found no way to disable it).