-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
chore(datadog_agent source, datadog_metrics sink): Add end to end tests with the Datadog Agent for metrics. #18840
chore(datadog_agent source, datadog_metrics sink): Add end to end tests with the Datadog Agent for metrics. #18840
Conversation
…tually validating anything
…nto neuronull/sink_datadog_metrics_v2_series_endpoint_conversion
…nto neuronull/sink_datadog_metrics_v2_series_endpoint_conversion
…ndpoint_conversion
This reverts commit c95a326.
…ndpoint_conversion
…ndpoint_conversion
19, 11, 6, 17, 5, 0, 1, 17, 17 | ||
] | ||
|
||
for i in range(50): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The framework in this PR is the bulk of the changes ... if anyone has suggestions on additional test cases to cover, that would be helpful. In theory the framework should hold up and we would just need to extend this code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A lot of suggestions below, but nothing really blocking given that this is just tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me at a high level
Adds end-to-end tests with the Datadog Agent for the
datadog_agent
source anddatadog_metrics
sink.This is an extension of #18538
The validation of metrics is more complex than logs.
The validation done is dependent on metric type. In all cases, we can't rely on the timestamps being the same.
Of note: in vector we currently still send to the
v1
endpoint. Once we convert to thev2
endpoint, some logic here can be removed which is converting the v1 JSON response into the protobuf response. Additionally the JSON response structs were required to be made visible to the e2e module.closes: #18535
epic: #18533