Commit 2e13a0d0 authored by Bob Van Landuyt's avatar Bob Van Landuyt

Decrease urgency for GraphQL

We now have a separate SLI that measures query duration. So we are
still monitoring the performance of single GraphQL queries. But there
could be multiple queries batched in a single request, causing the
request to take longer.

Lowering the urgency to account for multiple queries will improve the
`rails_requests` SLI.
parent aed836d7
......@@ -44,6 +44,13 @@ class GraphqlController < ApplicationController
# The default feature category is overridden to read from request
feature_category :not_owned
# We don't know what the query is going to be, so we can't set a high urgency
# See https://gitlab.com/groups/gitlab-org/-/epics/5841 for the work that will
# allow us to specify an urgency per query.
# Currently, all queries have a default urgency. And this is measured in the `graphql_queries`
# SLI. But queries could be multiplexed, so the total duration could be longer.
urgency :low, [:execute]
def execute
result = multiplex? ? execute_multiplex : execute_query
render json: result
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment