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

[Feature] Set MetricsStorage Address dynamically #2

Open
gebauerm opened this issue Jun 14, 2022 · 2 comments
Open

[Feature] Set MetricsStorage Address dynamically #2

gebauerm opened this issue Jun 14, 2022 · 2 comments
Assignees

Comments

@gebauerm
Copy link
Collaborator

As the metric storage is run on the localhost, where the benchmark is executed in the benchmark_runner, the address of the MetricStorage needs to be known in advance.
If a benchmark performs trails in pods or VMs the LatencyTracker might be znable to send results to the storage.

@gebauerm
Copy link
Collaborator Author

Use Env Variable in the resource definition as a fallback.
Automatically get the public IP in the benchmark runner.

@gebauerm gebauerm self-assigned this Jun 15, 2022
@gebauerm
Copy link
Collaborator Author

Can now be set via an Env Variable and is retrieved every time a LatencyTracker is initialized.

Will try out on the Optuna example once it is implemented.
Looking for a better solution

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

No branches or pull requests

1 participant