Prometheus adapter configuration for Linkerd

prometheus-adapter-linkerd.yaml

prometheus:
  url: http://linkerd-prometheus.linkerd.svc

rules:
  default: false
  custom:
    - seriesQuery: 'response_latency_ms_bucket{namespace!="",pod!=""}'
      resources:
        template: <<.Resource>>
      name:
        matches: ^(.*)_bucket$
        as: "${1}_50th"
      metricsQuery: histogram_quantile(0.50, sum(irate(<<.Series>>{<<.LabelMatchers>>, direction="inbound"}[5m])) by (le, <<.GroupBy>>))

    - seriesQuery: 'response_latency_ms_bucket{namespace!="",pod!=""}'
      resources:
        template: <<.Resource>>
      name:
        matches: ^(.*)_bucket$
        as: "${1}_95th"
      metricsQuery: histogram_quantile(0.95, sum(irate(<<.Series>>{<<.LabelMatchers>>, direction="inbound"}[5m])) by (le, <<.GroupBy>>))

    - seriesQuery: 'response_latency_ms_bucket{namespace!="",pod!=""}'
      resources:
        template: <<.Resource>>
      name:
        matches: ^(.*)_bucket$
        as: "${1}_99th"
      metricsQuery: histogram_quantile(0.99, sum(irate(<<.Series>>{<<.LabelMatchers>>, direction="inbound"}[5m])) by (le, <<.GroupBy>>))

    - seriesQuery: 'response_total{namespace!="",pod!=""}'
      resources:
        template: <<.Resource>>
      name:
        matches: "^(.*)_total$"
        as: "${1}_per_second"
      metricsQuery: |-
        sum(
          irate(
            <<.Series>>{
              <<.LabelMatchers>>,
              direction="inbound"
            }[5m]
          )
        ) by (
          <<.GroupBy>>
        )

Hey @geekyfox90,
read your article on medium https://medium.com/@boukhersy/auto-scale-your-services-with-custom-metrics-bffb071fb51f and cant thank you enough!

Sorry for the dumb question, but why is the metric called response_per_second while in your post you mentioned that you will listen for requests_per_second? Is there a way to get the request per second instead?