{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":394741638,"defaultBranch":"master","name":"cockroach","ownerLogin":"samiskin","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-08-10T18:10:24.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/6236424?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1693319007.0","currentOid":""},"activityList":{"items":[{"before":"28abface7fb3241b7733e3bacc55fee6006df535","after":"659b3761496340f68364b3669aeb8224b8c4b80d","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-29T18:46:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jayshrivastava","name":"Jayant","path":"/jayshrivastava","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/18633281?s=80&v=4"},"commit":{"message":"changefeedccl: add changefeed_progress and aggregator_progress sli metrics\n\nResolves #97009\n\nAn aggregator_progress sli metric has been added to track the timestamp\nprogress of each individual aggregator node, which can help identify single\naggregators that lag behind the rest.  A checkpoint_progress sli metric has\nalso been added to act in a similar capacity to max_behind_nanos.\n\nmax_behind_nanos can be removed but since this PR needs to be backported I left\nthe max_behind_nanos code untouched to be removed in a followup PR.\n\nI elected to keep everything as just the timestamp rather than a max_behind\nsetup since it's still possible in graphing tools to determine the lag (ex:\ngrafana query would be `time()*1000 -\n(changefeed_aggregator_progress{scope!=\"\"}/1000/1000))`.\n\nRelease note (ops change): changefeed metrics now include a\nchangefeed.checkpoint_progress metric which is similar to\nchangefeed.max_behind_nanos but supports metrics labels, as well as an\nchangefeed.aggregator_progress metric which can track the progress of\nindividual aggregators (the lowest timestamp for which all aggregators with the\nlabel have emitted all values they're responsible for).","shortMessageHtmlLink":"changefeedccl: add changefeed_progress and aggregator_progress sli me…"}},{"before":"ea44bbcf975215215e5e359f584b55843cb4314e","after":"28abface7fb3241b7733e3bacc55fee6006df535","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-29T17:05:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jayshrivastava","name":"Jayant","path":"/jayshrivastava","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/18633281?s=80&v=4"}},{"before":"8f5e6714062207ff186745ed3804454a2c708842","after":null,"ref":"refs/heads/backport22.2-102042","pushedAt":"2023-08-29T14:23:27.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"jayshrivastava","name":"Jayant","path":"/jayshrivastava","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/18633281?s=80&v=4"}},{"before":"a2648517030ea5e923bb048ba88bbd4342354ace","after":"ea44bbcf975215215e5e359f584b55843cb4314e","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-29T14:03:41.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"jayshrivastava","name":"Jayant","path":"/jayshrivastava","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/18633281?s=80&v=4"}},{"before":"2061f42f79b50bb23b612216730099357e85a7ea","after":"a2648517030ea5e923bb048ba88bbd4342354ace","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-28T19:36:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"5155c54ffb12f692fa06499e5628647e353c97e5","after":"c06505c35e8a828c288c81ff23d39ca434b7c1ff","ref":"refs/heads/clean-old-webhook-and-pubsub","pushedAt":"2023-08-28T19:34:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: remove old webhook and pubsub sink code\n\nThis PR removes the old webhook and pubsub implementations, having the v2 files\ntake their place.\n\nRelease note: The changefeed.new_webhook_sink_enabled and\nchangefeed.new_pubsub_sink_enabled settings have been removed as they are now\nalways enabled.","shortMessageHtmlLink":"changefeedccl: remove old webhook and pubsub sink code"}},{"before":null,"after":"5155c54ffb12f692fa06499e5628647e353c97e5","ref":"refs/heads/clean-old-webhook-and-pubsub","pushedAt":"2023-08-28T19:30:22.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"994dc2630139c2e7399bf558528f0e8799865227","after":"2061f42f79b50bb23b612216730099357e85a7ea","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-28T18:26:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"dc4aa3604b6fe89336d08d8ed30ac3ef5781e37b","after":"8fc3e1977f4da0c9e7eb245106a45c6c8ae5c55a","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T15:10:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add aggregator_lagging_ranges and aggregator_lagging_range_percentage metrics\n\nThis PR adds `aggregator_lagging_range_percentage`, and\n`aggregator_lagging_ranges` metrics to be able to measure the health of each\naggregator node individually over time.  A Lagging Ranges graph has also been\nadded to the db console page that just shows the total number of lagging ranges\nacross the cluster.\n\nEvery `changefeed.lagging_ranges_log_frequency` (default 2 minutes), each\naggregator will check each of its ranges, recording the total count, then\ncomparing them against its frontier to determine how many are behind by more\nthan `changefeed.lagging_ranges_threshold` (default 10 minutes).\n\nRelease note (ops change): New aggregator_lagging_range_percentage and\naggregator_lagging_ranges metrics have been added to track how many\nranges are behind a configurable changefeed.lagging_ranges_threshold\nduration.","shortMessageHtmlLink":"changefeedccl: add aggregator_lagging_ranges and aggregator_lagging_r…"}},{"before":"642c259485d75a353958ad0925365bffaa7bd965","after":"dc4aa3604b6fe89336d08d8ed30ac3ef5781e37b","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T15:05:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add aggregator_lagging_ranges and aggregator_lagging_range_percentage metrics\n\nThis PR adds `aggregator_lagging_range_percentage`, and\n`aggregator_lagging_ranges` metrics to be able to measure the health of each\naggregator node individually over time.  A Lagging Ranges graph has also been\nadded to the db console page that just shows the total number of lagging ranges\nacross the cluster.\n\nEvery `changefeed.lagging_ranges_log_frequency` (default 2 minutes), each\naggregator will check each of its ranges, recording the total count, then\ncomparing them against its frontier to determine how many are behind by more\nthan `changefeed.lagging_ranges_threshold` (default 10 minutes).\n\nRelease note (ops change): New aggregator_range_health and\naggregator_lagging_ranges metrics have been added to track how many ranges are\nbehind a configurable changefeed.lagging_ranges_threshold duration.","shortMessageHtmlLink":"changefeedccl: add aggregator_lagging_ranges and aggregator_lagging_r…"}},{"before":"3f31ddfcd1de69b39b0dae26dd5b93a9e8c887b5","after":"642c259485d75a353958ad0925365bffaa7bd965","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T14:57:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"d4f7dc79d741835919e613638e91dfda447917bc","after":"3f31ddfcd1de69b39b0dae26dd5b93a9e8c887b5","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T14:54:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"8881233d6422434ecb3c89494904f86402827f48","after":"d4f7dc79d741835919e613638e91dfda447917bc","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T08:05:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"0ab1b02b8f9dcd89425dde5af8d0849c211cf90f","after":"8881233d6422434ecb3c89494904f86402827f48","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-08-28T08:04:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"04b2297e01d0aada8aed0b9f1e28600352b1707d","after":"cc515db715801e19bd7ff19ee35c15741330365e","ref":"refs/heads/azure-roachtest","pushedAt":"2023-08-28T06:10:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add azure event hub roachtest\n\nResolves #100815\n\nThis PR adds a roachtest to verify that we are able to stream to Azure\nEvent Hubs via their Kafka endpoint.\n\nTo do this in roachtests, the following was created in our CRL Azure org:\n- The resource group \"cdc-testing\"\n- The Event Hubs Namespace \"roachtest-cdc\"\n- The Event Hub \"testing\" (within the \"roachtest-cdc\" namespace)\n- The SAS policy \"roachtest\"\n\nThe \"Event Hub\" called \"testing\" is equivalent to a Kafka Topic.\n\nRunning the roachtest requires the Azure CLI to be installed (you'd see\nthis error trying to create the Azure cluster in the first place).\n\nNote that this test will not run automatically in nightlies as Azure\nroachtests are blocked on #58668, this roachtest can only be ran\nmanually for now.\n\nRelease note: None","shortMessageHtmlLink":"changefeedccl: add azure event hub roachtest"}},{"before":"f5e649a26e3c245803b78c5a68b27fbacbc5e91e","after":"994dc2630139c2e7399bf558528f0e8799865227","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-24T18:25:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add changefeed_progress and aggregator_progress sli metrics\n\nResolves #97009\n\nAn aggregator_progress sli metric has been added to track the timestamp\nprogress of each individual aggregator node, which can help identify single\naggregators that lag behind the rest.  A checkpoint_progress sli metric has\nalso been added to act in a similar capacity to max_behind_nanos.\n\nmax_behind_nanos can be removed but since this PR needs to be backported I left\nthe max_behind_nanos code untouched to be removed in a followup PR.\n\nI elected to keep everything as just the timestamp rather than a max_behind\nsetup since it's still possible in graphing tools to determine the lag (ex:\ngrafana query would be `time()*1000 -\n(changefeed_aggregator_progress{scope!=\"\"}/1000/1000))`.\n\nRelease note (ops change): changefeed metrics now include a\nchangefeed.checkpoint_progress metric which is similar to\nchangefeed.max_behind_nanos but supports metrics labels, as well as an\nchangefeed.aggregator_progress metric which can track the progress of\nindividual aggregators (the lowest timestamp for which all aggregators with the\nlabel have emitted all values they're responsible for).","shortMessageHtmlLink":"changefeedccl: add changefeed_progress and aggregator_progress sli me…"}},{"before":"6bc670192d36eeb06589e2760655183b37261c3c","after":"2f47d864385383210cb5d442378e4897c04a0844","ref":"refs/heads/public-new-webhook-pubsub-sink","pushedAt":"2023-08-24T16:41:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: enable new webhook and pubsub sinks by default\n\nResolves #108806\n\nThis PR enables the new webhook and pubsub sink implementations by default.\nLeaving the settings in existence for near future in case something does go\nwrong, but I did not set them to public since there's no normal-operation\nreason to disable them.\n\nRelease note (performance improvement): changefeeds to webhook or pubsub\nendpoints now support much higher throughput","shortMessageHtmlLink":"changefeedccl: enable new webhook and pubsub sinks by default"}},{"before":null,"after":"6bc670192d36eeb06589e2760655183b37261c3c","ref":"refs/heads/public-new-webhook-pubsub-sink","pushedAt":"2023-08-23T17:02:46.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"1b137086bb36d544b813244df4511e6716bb9c37","after":"f5e649a26e3c245803b78c5a68b27fbacbc5e91e","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-21T03:40:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add changefeed_progress and aggregator_progress sli metrics\n\nResolves #97009\n\nAn aggregator_progress sli metric has been added to track the timestamp\nprogress of each individual aggregator node, which can help identify single\naggregators that lag behind the rest.  A checkpoint_progress sli metric has\nalso been added to act in a similar capacity to max_behind_nanos.\n\nmax_behind_nanos can be removed but since this PR needs to be backported I left\nthe max_behind_nanos code untouched to be removed in a followup PR.\n\nI elected to keep everything as just the timestamp rather than a max_behind\nsetup since it's still possible in graphing tools to determine the lag (ex:\ngrafana query would be `time()*1000 -\n(changefeed_aggregator_progress{scope!=\"\"}/1000/1000))`.\n\nRelease note (ops change): changefeed metrics now include a checkpoint_progress\nmetric which is similar to max_behind_nanos but supports metrics labels, as\nwell as an aggregator_progress metric which can track the progress of\nindividual aggregators (the lowest timestamp for which all aggregators with the\nlabel have emitted all values they're responsible for).","shortMessageHtmlLink":"changefeedccl: add changefeed_progress and aggregator_progress sli me…"}},{"before":null,"after":"1b137086bb36d544b813244df4511e6716bb9c37","ref":"refs/heads/checkpoint-progress-backport","pushedAt":"2023-08-15T05:05:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add changefeed_progress and aggregator_progress sli metrics\n\nResolves #97009\n\nAn aggregator_progress sli metric has been added to track the timestamp\nprogress of each individual aggregator node, which can help identify single\naggregators that lag behind the rest.  A checkpoint_progress sli metric has\nalso been added to act in a similar capacity to max_behind_nanos.\n\nI elected to keep everything as just the timestamp rather than a max_behind\nsetup since it's still possible in graphing tools to determine the lag (ex:\ngrafana query would be `time()*1000 -\n(changefeed_aggregator_progress{scope!=\"\"}/1000/1000))`.\n\nRelease note (ops change): changefeed metrics now include checkpoint_progress\nand aggregator_progress metrics to track the timestamp of the changefeed's\npersisted checkpoint and each individual aggregators progress.\ncheckpoint_progress can be used for a similar purpose to max_behind_nanos but\nnow with support for per-changefeed metrics labels.","shortMessageHtmlLink":"changefeedccl: add changefeed_progress and aggregator_progress sli me…"}},{"before":"5dee7503635e3dc488e842f12a8939a01406baad","after":"a6ac63770b4168f584246de51260786d786280c7","ref":"refs/heads/arm-roachtest","pushedAt":"2023-08-08T14:58:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: enable changefeed tests on ARM\n\nThis change enables all changefeed tests on ARM except for the Kafka\nOAuth test.  There are only Kafka 3 ARM binaries available, which are\ninternally ran via docker, but the OAuth test requires Kafka 2 for the\nbroker setup.\n\nRelease note: None","shortMessageHtmlLink":"changefeedccl: enable changefeed tests on ARM"}},{"before":"7583bd47c469d6687c4df65171a606b333d4ce27","after":"5dee7503635e3dc488e842f12a8939a01406baad","ref":"refs/heads/arm-roachtest","pushedAt":"2023-08-03T15:22:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: enable changefeed tests on ARM\n\nThis change enables all changefeed tests on ARM except for the Kafka\nOAuth test.  There are only Kafka 3 ARM binaries available, which are\ninternally ran via docker, but the OAuth test requires Kafka 2 for the\nbroker setup.\n\nRelease note: None","shortMessageHtmlLink":"changefeedccl: enable changefeed tests on ARM"}},{"before":"c4d76f1a3781fa3676d6dd38907390fe965c17ee","after":"7583bd47c469d6687c4df65171a606b333d4ce27","ref":"refs/heads/arm-roachtest","pushedAt":"2023-08-03T15:10:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"e375ab4a96c963a81dc6d6f3e880a71dec2a2185","after":"c4d76f1a3781fa3676d6dd38907390fe965c17ee","ref":"refs/heads/arm-roachtest","pushedAt":"2023-08-03T14:54:19.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":null,"after":"e375ab4a96c963a81dc6d6f3e880a71dec2a2185","ref":"refs/heads/arm-roachtest","pushedAt":"2023-08-03T14:28:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"aff594b0ca415dddee656131cdcf122c4617d2fb","after":"04b2297e01d0aada8aed0b9f1e28600352b1707d","ref":"refs/heads/azure-roachtest","pushedAt":"2023-06-28T22:30:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add azure event hub roachtest\n\nResolves #100815\n\nThis PR adds a roachtest to verify that we are able to stream to Azure\nEvent Hubs via their Kafka endpoint.\n\nTo do this in roachtests, the following was created in our CRL Azure org:\n- The resource group \"cdc-testing\"\n- The Event Hubs Namespace \"roachtest-cdc\"\n- The Event Hub \"testing\" (within the \"roachtest-cdc\" namespace)\n- The SAS policy \"roachtest\"\n\nThe \"Event Hub\" called \"testing\" is equivalent to a Kafka Topic.\n\nRunning the roachtest requires the Azure CLI to be installed (you'd see\nthis error trying to create the Azure cluster in the first place).\n\nNote that this test will not run automatically in nightlies as Azure\nroachtests are blocked on #58668, this roachtest can only be ran\nmanually for now.\n\nRelease note: None","shortMessageHtmlLink":"changefeedccl: add azure event hub roachtest"}},{"before":"f5c51249ab7d8400d28f43f2e8c6c748045bfe09","after":"aff594b0ca415dddee656131cdcf122c4617d2fb","ref":"refs/heads/azure-roachtest","pushedAt":"2023-06-26T21:05:06.028Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add azure event hub roachtest\n\nResolves #100815\n\nThis PR adds a roachtest to verify that we are able to stream to Azure\nEvent Hubs via their Kafka endpoint.\n\nTo do this in roachtests, the following was created in our CRL Azure org:\n- The resource group \"cdc-testing\"\n- The Event Hubs Namespace \"roachtest-cdc\"\n- The Event Hub \"testing\" (within the \"roachtest-cdc\" namespace)\n- The SAS policy \"roachtest\"\n\nThe \"Event Hub\" called \"testing\" is equivalent to a Kafka Topic.\n\nRunning the roachtest requires the Azure CLI to be installed (you'd see\nthis error trying to create the Azure cluster in the first place).\n\nNote that this test will not run automatically in nightlies as Azure\nroachtests are blocked on #58668, this roachtest can only be ran\nmanually for now.\n\nRelease note: None","shortMessageHtmlLink":"changefeedccl: add azure event hub roachtest"}},{"before":"f64a5ed64e49d9c12ba87f30dbaf323a20cda0dc","after":"f5c51249ab7d8400d28f43f2e8c6c748045bfe09","ref":"refs/heads/azure-roachtest","pushedAt":"2023-06-26T20:35:32.766Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":null,"after":"f64a5ed64e49d9c12ba87f30dbaf323a20cda0dc","ref":"refs/heads/azure-roachtest","pushedAt":"2023-06-26T20:25:17.723Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"}},{"before":"0c450b1656a638f03a19838c906264aa1f7b8394","after":"0ab1b02b8f9dcd89425dde5af8d0849c211cf90f","ref":"refs/heads/lagging-range-metrics","pushedAt":"2023-06-22T18:17:45.111Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"samiskin","name":"Shiranka Miskin","path":"/samiskin","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6236424?s=80&v=4"},"commit":{"message":"changefeedccl: add lagging_ranges, range_health, progress metrics\n\nThis PR adds `aggregator_range_health`, `aggregator_lagging_ranges`, and\n`aggregator_progress` metrics to be able to measure the health of each\naggregator node individually over time.  A Lagging Ranges graph has also been\nadded to the db console page that just shows the total number of lagging ranges\nacross the cluster.\n\nA `checkpoint_progress` sli metric has also been added to act in a similar\ncapacity to max_behind_nanos.  I elected to keep it as just the timestamp since\nit's still possible in graphing tools to determine the lag (ex: grafana query\nwould be `time()*1000 -\n(changefeed_aggregator_progress{scope!=\"\"}/1000/1000)`).\n\nEvery `changefeed.lagging_ranges_log_frequency` (default 2 minutes), each\naggregator will check each of its ranges, recording the total count, then\ncomparing them against its frontier to determine how many are behind by more\nthan `changefeed.lagging_ranges_threshold` (default 10 minutes).\n\nRelease note (ops change): New aggregator_range_health and\naggregator_lagging_ranges metrics have been added to track how many ranges are\nbehind a configurable changefeed.lagging_ranges_threshold duration.\ncheckpoint_progress and aggregator_progress metrics have also been added to\ntrack the timestamp of the changefeed's persisted checkpoint and each\nindividual aggregators progress. checkpoint_progress can be used for a similar\npurpose to max_behind_nanos but now with support for per-changefeed metrics\nlabels.","shortMessageHtmlLink":"changefeedccl: add lagging_ranges, range_health, progress metrics"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wOC0yOVQxODo0Njo1NS4wMDAwMDBazwAAAAN1JYLP","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNi0yMlQxODoxNzo0NS4xMTE0OTFazwAAAANHIR0S"}},"title":"Activity · samiskin/cockroach"}