-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[NDINT-290] Versa SLA Metrics w/ Session Auth #37300
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
Conversation
// generateDeviceNameToIDMap generates a map of device ID to device name to enrich the results from Analytics responses | ||
func generateDeviceNameToIDMap(deviceMetadata []devicemetadata.DeviceMetadata) map[string]string { | ||
deviceNameToIDMap := make(map[string]string) | ||
// TODO: should we convert the tags map to use ID instead of IP? |
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.
woops totally valid, i think device_id probably is better here? 🤦 id/ip really mixed up easily
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.
not blocker for the pr, but agree! thanks for adding this todo
|
||
// Request to /versa/analytics/login to obtain Analytics CSRF prevention token | ||
analyticsPayload := url.Values{} | ||
analyticsPayload.Set("endpoint", client.analyticsEndpoint) // TODO: WHY? Where can we get this for others? |
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.
non blocking question
i forget if during our 1:1 you made a successful call to /versa/login
that doesn't require this endpoint
parameter but if i recall correctly, returns the token we're looking for?
tbh it's very close to this /versa/analytics/login
so maybe i mixed it up 🤔
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 flow requires the analytics endpoint parameter to be set. I haven't been able to get that version working, it's something I'm going to look at when I get back.
@@ -162,6 +152,16 @@ func (v *VersaCheck) Run() error { | |||
v.metricsSender.SendDirectorStatus(directorStatus) | |||
} | |||
|
|||
// Temporarily commenting out the SLA metrics collection until Versa Analytics auth is sorted out |
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.
we can remove this comment if the metrics are flowing in ok!
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: e1d209a Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | ddot_metrics | memory utilization | +0.19 | [+0.07, +0.31] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.13 | [-0.48, +0.75] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.06 | [-0.55, +0.68] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.05 | [-0.53, +0.62] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.04 | [-0.57, +0.64] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.25, +0.26] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.00 | [-0.58, +0.57] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.03 | [-0.27, +0.20] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.05 | [-0.66, +0.55] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.07 | [-0.17, +0.03] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -0.12 | [-2.83, +2.59] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.15 | [-0.78, +0.47] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.27 | [-0.42, -0.13] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.40 | [-0.53, -0.27] | 1 | Logs bounds checks dashboard |
➖ | otlp_ingest_metrics | memory utilization | -0.62 | [-0.78, -0.46] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.68 | [-3.61, +2.25] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.74 | [-0.82, -0.66] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.92 | [-1.04, -0.79] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -1.09 | [-1.15, -1.02] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.17 | [-1.22, -1.11] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.49 | [-2.32, -0.66] | 1 | Logs |
➖ | file_tree | memory utilization | -2.01 | [-2.20, -1.83] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
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.
lgtmmm ty for re-adding !!
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
[email protected] unqueued this merge request |
/merge -c |
View all feedbacks in Devflow UI.
|
At this point, the logic in |
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
What does this PR do?
Adds back support for session and CSRF token based authentication to allow calls to Versa analytics APIs which do not support HTTP Basic Auth.
With this change, we can enable collection of the SLA metrics from a previous PR.
Session/Token auth is only used when SLA metrics are being called for, basic auth is still the default for now.
Motivation
Describe how you validated your changes
Ran the agent locally against our own Versa cluster.
Possible Drawbacks / Trade-offs
Additional Notes