feat: revert to otel instrumentation (#17)

Author: Sébastien Dan

.env.example

@@ -2,10 +2,11 @@ AUTH0_AUDIENCE=
 AUTH0_ISSUER_URL=
 REDIS_HOST=
 REDIS_PORT=
-TOPOS_SUBNET_ENDPOINT_WS=
 SUBNET_REGISTRATOR_CONTRACT_ADDRESS=
 TOPOS_CORE_PROXY_CONTRACT_ADDRESS=
-TRACING_SERVICE_NAME=
-TRACING_SERVICE_VERSION=
-ELASTIC_APM_ENDPOINT=
-ELASTIC_APM_TOKEN=
+TOPOS_SUBNET_ENDPOINT_WS=
+
+# telemetry
+OTEL_EXPORTER_OTLP_ENDPOINT=
+OTEL_SERVICE_NAME=
+OTEL_SERVICE_VERSION=

.github/workflows/test.yml

@@ -22,9 +22,6 @@ jobs:
 
       - run: npm ci
       - run: npm run test
-        env:
-          ELASTIC_APM_ENDPOINT: ${{ secrets.ELASTIC_APM_ENDPOINT }}
-          ELASTIC_APM_TOKEN: ${{ secrets.ELASTIC_APM_TOKEN }}
 
   e2e-tests:
     name: E2E tests
@@ -45,5 +42,3 @@ jobs:
           REDIS_HOST: ${{ vars.REDIS_HOST }}
           REDIS_PORT: ${{ vars.REDIS_PORT }}
           PRIVATE_KEY: ${{ secrets.PRIVATE_KEY }}
-          ELASTIC_APM_ENDPOINT: ${{ secrets.ELASTIC_APM_ENDPOINT }}
-          ELASTIC_APM_TOKEN: ${{ secrets.ELASTIC_APM_TOKEN }}

README.md

@@ -33,17 +33,6 @@ The Executor Service requires a local environment to be set up.
 
 Create an `.env` at the root of the project, with the content of `.env.example`, and fill the revelant env var values.
 
-```
-AUTH0_AUDIENCE=
-AUTH0_ISSUER_URL=
-REDIS_HOST=
-REDIS_PORT=
-TOPOS_SUBNET_ENDPOINT_WS=
-SUBNET_REGISTRATOR_CONTRACT_ADDRESS=
-TOPOS_CORE_PROXY_CONTRACT_ADDRESS=
-ERC20_MESSAGING_CONTRACT_ADDRESS=
-```
-
 ### Authentication (Auth0)
 
 The Executor Service leverages [Auth0](https://auth0.com/) for machine-to-machine authentication and authorization. We use Auth0's machine-to-machine service as we are not authenticating/authorizing users but applications (e.g., dApp frontends) that will use the Executor Service as a call delegation for their users' cross-subnet messages.