Skip to content
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.

Commit

Permalink
feat: revert to otel instrumentation (#17)
Browse files Browse the repository at this point in the history
  • Loading branch information
sebastiendan authored Nov 7, 2023
1 parent 34d5cce commit f3ae2c2
Show file tree
Hide file tree
Showing 19 changed files with 1,539 additions and 392 deletions.
11 changes: 6 additions & 5 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -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=
5 changes: 0 additions & 5 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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 }}
11 changes: 0 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading

0 comments on commit f3ae2c2

Please sign in to comment.