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

feat: add chain name config #74

Merged
merged 4 commits into from
Oct 19, 2022
Merged

feat: add chain name config #74

merged 4 commits into from
Oct 19, 2022

Conversation

IvanVergiliev
Copy link
Contributor

Description

Add required ChainName config and set it as a label in logs and metrics.

Type of change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 😎 New feature (non-breaking change which adds functionality)
  • ⁉️ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • ⚒️ Refactor (no functional changes)
  • 📖 Documentation (updating or adding docs)

@IvanVergiliev IvanVergiliev force-pushed the multi-chain-config-name branch 2 times, most recently from 31c085e to e50eb31 Compare October 19, 2022 22:36
Base automatically changed from multi-chain-logging to main October 19, 2022 22:37
@IvanVergiliev
Copy link
Contributor Author

Ignoring lint failure because the relevant code changes in the next PR.

@IvanVergiliev IvanVergiliev merged commit 0cd76c6 into main Oct 19, 2022
@IvanVergiliev IvanVergiliev deleted the multi-chain-config-name branch October 19, 2022 22:46
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