You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GraphQL scaler trigger scales based on a metric value provided by an GraphQL API.
It uses GraphQL API as a metric provider.
The interface that users interact with:
triggers:
- type: graphql
metadata:
targetValue: "8.8"
query: |
query {
usage{
target_number
}
}
activationTargetValue: "3.8"
url: "http://graphql:6666"
valueLocation: "data.usage.1.target_number" # GJSON path notation to extract the metric value
Scaler Source
GraphQL API
Scaling Mechanics
Metric value provided by an GraphQL API
Authentication Source
basic, TLS, OAuth 2.0 and token
Anything else?
I am aware of the existence of metrics API scaler. The scaler in question, for obvious reasons, uses the GET method and therefore does not allow passing request bodies. On the other hand, GraphQL by definition uses the POST method (although some libraries support GET), and in many cases, the query is sent in the body of the request. I believe that modifying the scaler to enable the execution of GraphQL queries is not ideal, as it changes the concept of the scaler.
The text was updated successfully, but these errors were encountered:
Proposal
GraphQL scaler trigger scales based on a metric value provided by an GraphQL API.
It uses GraphQL API as a metric provider.
The interface that users interact with:
Scaler Source
GraphQL API
Scaling Mechanics
Metric value provided by an GraphQL API
Authentication Source
basic, TLS, OAuth 2.0 and token
Anything else?
I am aware of the existence of metrics API scaler. The scaler in question, for obvious reasons, uses the GET method and therefore does not allow passing request bodies. On the other hand, GraphQL by definition uses the POST method (although some libraries support GET), and in many cases, the query is sent in the body of the request. I believe that modifying the scaler to enable the execution of GraphQL queries is not ideal, as it changes the concept of the scaler.
The text was updated successfully, but these errors were encountered: