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

Track vendor and version of the VCs used in our clusters #3107

Closed
5 tasks
boulder225 opened this issue May 29, 2024 · 2 comments
Closed
5 tasks

Track vendor and version of the VCs used in our clusters #3107

boulder225 opened this issue May 29, 2024 · 2 comments
Assignees
Labels
protocol Protocol Team tickets

Comments

@boulder225
Copy link

🎯 Problem to be solved

There is a need to track the vendor and version information of the VCs used in our clusters. Currently, this information is not being tracked or monitored.

The natural idea is to track User-Agent header we receive in VAPI, e.g.
"key": "User-Agent", "values": "nim-presto/0.0.3 (arm64/linux)"

🛠️ Proposed solution

  • Investigate the User-Agent header received in VAPI requests from different VCs to see if it contains reliable vendor and version information.
  • If the User-Agent header provides the required information, implement a mechanism to extract and store the vendor and version details from the header.
  • If the User-Agent header is not a reliable source, explore alternative methods to retrieve the vendor and version information from the VCs.
  • Create a metric or monitoring system to track and display the vendor and version information of the VCs used in our clusters.
  • Implement alerting or notification mechanisms if specific vendor or version combinations are encountered or if certain versions are outdated or known to have issues.
@github-actions github-actions bot added the protocol Protocol Team tickets label May 29, 2024
@boulder225
Copy link
Author

Hey team! Please add your planning poker estimate with Zenhub @gsora @KaloyanTanev @pinebit

obol-bulldozer bot pushed a commit that referenced this issue Jun 3, 2024
Added two new metrics to VAPI:
* core_validatorapi_request_total
* core_validatorapi_vc_user_agent

These will allows us to track VC's User-Agent strings to determine VC vendor/version implicitly.
And the total number of requests have Content-Type label to track requests' format made by VC.

category: feature
ticket: #3107
@pinebit
Copy link
Contributor

pinebit commented Jun 28, 2024

Done with #3112

@pinebit pinebit closed this as completed Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

2 participants