Move GraphGL semconv out of DB folder

[lmolkova]

graphql.operation.name	string	The name of the operation being executed.	findBookById	Recommended

Should be covered by db.operation.

[lmolkova]

It seems there were no discussions on this in open-telemetry/opentelemetry-specification#2456 when it was introduced.

@laurit do you happen to remember if there was a specific reason to add a new attribute?

[lmolkova]

Also, graphql does not extend db in yaml and does not put its attributes into db. namespace. Is it intentional?

[laurit]

@laurit do you happen to remember if there was a specific reason to add a new attribute?

I believe I used the attribute names from the nodjs graphql instrumentation.

Also, graphql does not extend db in yaml and does not put its attributes into db. namespace. Is it intentional?

As far as I remember treating graphql as, or as a subset, of db was not considered during the review.

[joaopgrassi]

Well, I guess there we have some breaking changes :D

[trask]

it's not clear to me the criteria for GraphQL being grouped under databases?

[crsantos]

Honest question, why does it need to be under db.?

[lmolkova]

Honest question, why does it need to be under db.?

If we don't consider GraphQL to be a database, it would totally be fine to not add db., but then we need to remove it from database folder (semantic-conventions/blob/main/docs/database/graphql.md)

and stop listing it under DB semconv

semantic-conventions/docs/database/README.md

Line 27 in 44c830d

* [GraphQL](graphql.md): Semantic Conventions for *GraphQL Server*.

Both options work for me.

[crsantos]

but then we need to remove it from database folder

Oh, I didn't know its location. Thanks.

I agree on moving it.

IMHO, it should have its own folder, since it doesn't seem to fit into any other existing one.