Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BCI-2588: Changes for STOM #361

Merged
merged 2 commits into from
Feb 27, 2024
Merged

BCI-2588: Changes for STOM #361

merged 2 commits into from
Feb 27, 2024

Conversation

augustbleeds
Copy link
Collaborator

@augustbleeds augustbleeds commented Feb 20, 2024

With these changes, STOM works locally.

STOM is basically a service that will pull config data from a http endpoint & environmental variables to determine what contracts to monitor. Then it will publish data to a local prometheus http server it creates and kafka topic.

Briefly, here's what I did

1. Run soak test in terminal 1
2. Modify ENV vars & /tmp/config directory with values of Link address, Ocr address, Proxy address
3. In terminal 2, start config http server
4. In terminal 3, start kafka server (docker compose up)
5. Wait until the ocr rounds start
6. In terminal 4, source ENV vars in step 2 and start the monitoring service

Now that we know the monitoring plugin and relayer integration works smoothly locally, I'll create a ticket for testnet deployment to make sure that the

  1. http config files are updated
  2. kafka topic is still provisioned
  3. monitoring k8s deployment is deployed

archseer
archseer previously approved these changes Feb 26, 2024
@archseer archseer merged commit 4c6911c into develop Feb 27, 2024
14 of 19 checks passed
@archseer archseer deleted the BCI-25888/stom-works branch February 27, 2024 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants