Skip to content

CNDB-18356: include CAS latency metrics in allRequests metrics#2497

Merged
driftx merged 1 commit into
main-5.0from
CNDB-18356
Jul 1, 2026
Merged

CNDB-18356: include CAS latency metrics in allRequests metrics#2497
driftx merged 1 commit into
main-5.0from
CNDB-18356

Conversation

@driftx

@driftx driftx commented Jun 30, 2026

Copy link
Copy Markdown

What is the issue

allRequest metrics are missing CAS latencies

What does this PR fix and why was it fixed

includes CAS latency metrics in allRequests metrics

@github-actions

Copy link
Copy Markdown

Checklist before you submit for review

  • This PR adheres to the Definition of Done
  • Make sure there is a PR and ticket in the CNDB project updating the Converged Cassandra version
  • Use NoSpamLogger for log lines that may appear frequently in the logs
  • Verify test results on Butler
  • Test coverage for new/modified code is > 80%
  • Proper code formatting
  • Proper title for each commit staring with the project-issue number, like CNDB-1234
  • Each commit has a meaningful description
  • Each commit is not very long and contains related changes
  • Renames, moves and reformatting are in distinct commits
  • All new files should contain the IBM copyright header instead of the Apache License one (no DataStax copyright any longer)

@plpesvc-ds

Copy link
Copy Markdown

❌ Build ds-cassandra-pr-gate/PR-2497 rejected by Butler


2 regressions found
See build details here


Found 2 new test failures

Test Explanation Runs Upstream
o.a.c.index.sai.cql.VectorCompaction100dTest.testOneToOneCompaction[version=ec enableNVQ=false] () NEW 🔴 0 / 30
o.a.c.index.sai.cql.VectorSiftSmallTest.testSiftSmall[ed false] () NEW 🔴 0 / 30

Found 2 known test failures

@driftx driftx merged commit bfb4ab7 into main-5.0 Jul 1, 2026
4 of 6 checks passed
@driftx driftx deleted the CNDB-18356 branch July 1, 2026 12:18
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

Successfully merging this pull request may close these issues.

3 participants