218f8adc8f
Add a per-scheduling-group gauge that tracks the number of in-flight CQL requests for each service level. The existing scylla_transport_requests_serving metric is a single global per-shard counter; the new metric breaks it down by scheduling group so operators can see which service level contributes the most in-flight requests when debugging latency. The metric is named cql_requests_serving (exposed as scylla_transport_cql_requests_serving) following the cql_ prefix convention used by all other per-scheduling-group transport metrics (cql_requests_count, cql_request_bytes, cql_response_bytes, cql_pending_response_memory). Using a cql_ prefix avoids Prometheus confusion with the global requests_serving metric, which lacks the scheduling_group_name label. The counter is incremented when a request enters process_request() and decremented in the same 'leave' defer block as the global requests_serving, ensuring the request is counted as in-flight until the response is sent.
Scylla in-source tests.
For details on how to run the tests, see docs/dev/testing.md
Shared C++ utils, libraries are in lib/, for Python - pylib/
alternator - Python tests which connect to a single server and use the DynamoDB API unit, boost, raft - unit tests in C++ cqlpy - Python tests which connect to a single server and use CQL topology* - tests that set up clusters and add/remove nodes cql - approval tests that use CQL and pre-recorded output rest_api - tests for Scylla REST API Port 9000 scylla-gdb - tests for scylla-gdb.py helper script nodetool - tests for C++ implementation of nodetool
If you can use an existing folder, consider adding your test to it. New folders should be used for new large categories/subsystems, or when the test environment is significantly different from some existing suite, e.g. you plan to start scylladb with different configuration, and you intend to add many tests and would like them to reuse an existing Scylla cluster (clusters can be reused for tests within the same folder).
To add a new folder, create a new directory, and then
copy & edit its suite.ini.