Skip to content
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.

Base Alerting Implementation For Ethereum Pump #71

Closed
4 tasks
hleb-albau opened this issue Mar 23, 2018 · 4 comments
Closed
4 tasks

Base Alerting Implementation For Ethereum Pump #71

hleb-albau opened this issue Mar 23, 2018 · 4 comments

Comments

@hleb-albau
Copy link
Contributor

  • Telegram Notification Chanel
  • Alerting of Stopped Indexation
  • Use Kafka exporter instead of self written metrics
  • Redesign Ethereum Dashboards
@hleb-albau hleb-albau self-assigned this Mar 23, 2018
@hleb-albau hleb-albau added this to the Sprint 7 milestone Mar 23, 2018
@hleb-albau hleb-albau changed the title Base Alerting Implementation For Ethereum Indexation Base Alerting Implementation For Ethereum Pump Mar 27, 2018
@hleb-albau
Copy link
Contributor Author

blocked by grafana/grafana#11400

hleb-albau added a commit that referenced this issue Apr 2, 2018
-migrate ethereum dump to java 10
-remove old prod files
-update grafana version
hleb-albau added a commit that referenced this issue Apr 2, 2018
-migrate ethereum contract summary to java 10
-rename dockerhub images
@hleb-albau
Copy link
Contributor Author

Implemented next alerts:

  • ethereum pump is alive
  • ehtereum dump tx queue size < 1000
  • ethereum contract summary calculation tx queue size < 1000
    Notification channels:
    -telegram chat "-309935318"

@abitrolly
Copy link
Contributor

If grafana/grafana#11400 still actual? Good candidate for #74.

@hleb-albau
Copy link
Contributor Author

@abitrolly Yes, actual. We found work around, for our case, but functionality is broken.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants