Experiment with lading telemetry via UDS #908
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This stack of pull requests is managed by Graphite. Learn more about stacking. |
blt
force-pushed
the
blt/experiment_with_lading_telemetry_via_uds
branch
3 times, most recently
from
1d4fd40
to
3fb3147
Compare
blt
changed the base branch from
blt/allow_for_effectively_infinite_experiment_duration
to
blt/update_metrics-rs_crate
Merged
blt
force-pushed
the
blt/experiment_with_lading_telemetry_via_uds
branch
2 times, most recently
from
14d311c
to
a84a99c
Compare
blt
force-pushed
the
blt/update_metrics-rs_crate
branch
from
b76eaf3
to
eb0fc35
Compare
blt
force-pushed
the
blt/experiment_with_lading_telemetry_via_uds
branch
from
a84a99c
to
aeb3884
Compare
This commit updates our use of the metrics-rs crate to latest, putting us in position to make use of upstream features in the near-term. Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
We have a need for some lading installations to punch telemetry from inside a isolated VM or container where only a FS mount is available. This commit introduces a proof of concept -- in a rough state -- that shows it's possible for us to create a gauge, counter telemetry stream with registered contexts to avoid sending the same strings repeatedly over the socket with minimal coordination between peers. It's clear some sort of abstraction is still missing here, but it's a start. Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
blt
force-pushed
the
blt/update_metrics-rs_crate
branch
from
eb0fc35
to
9e7ce5c
Compare
blt
force-pushed
the
blt/experiment_with_lading_telemetry_via_uds
branch
from
aeb3884
to
b14ff74
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Experiment with lading telemetry via UDS
We have a need for some lading installations to punch telemetry from inside a isolated VM or container where only a FS mount is available. This commit introduces a proof of concept -- in a rough state -- that shows it's possible for us to create a gauge, counter telemetry stream with registered contexts to avoid sending the same strings repeatedly over the socket with minimal coordination between peers.
It's clear some sort of abstraction is still missing here, but it's a start.