hasura / hasura/graphql-engine
Operation name error in Hasura Cloud monitoring
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Noticing a few issues with the way the operation name is picked up the Cloud monitoring UI (backend).
### Steps to reproduce issue
1. Create a RESTified endpoint with a named operation as follows:
```
query v1ApiResponse {
articles {
id
title
}
}
```
2. Hit the REST endpoint using a client.
3. Head to the monitoring section and check out the operation name:

4. Change the name of the query to something like `V1ApiResponse`: you should see the pattern here with the operation name reported as `V`.
Also, shouldn't the operation type of this call be something different compared to a regular GraphQL operation - e.g. `REST/query` instead of just `query`.
Contributor guide
Research direction
Start by reproducing the RESTified endpoint case in the issue and inspect how the Cloud monitoring UI derives operation names and types for that request. Done means the full named operation is reported rather than its first character, and the operation type is correctly distinguished from a regular GraphQL operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100