Make sure elasticsearch instrumentation follows semantic conventions

[srikanthccv]

No description provided.

[remram44]

Re-posting the details here, since you closed the earlier issue in favor of a later one with a blank description.

A bit rude to be honest, you make contributors fill out an extensive template, and then you overrule them with empty tickets.

---

Describe your environment
Using opentelemetry-instrumentation-elasticsearch 0.24b0 with elasticsearch 7.14.1

What is the expected behavior?
The instrumentation should follow the semantic conventions for database clients, notably use span names in the format <db.operation> <db.name>.<db.sql.table>.

What is the actual behavior?
Span names are built from the request URL without any form of parsing. In particular, the operation (index/delete/...) is missing, and the database name is not necessarily present.

Example span names:

• Elasticsearch/indexname/_doc/documentid (insert operation if PUT, read operation if GET)
• Elasticsearch/indexname/_doc (probably an insert without a set primary key)
• Elasticsearch/indexname (either reading metadata or changing schema/settings), Elasticsearch/indexname/_search (query operation)

Many attributes are also missing or are only present in the request path, because they get encoded in the URL before perform_request() is called, which is the only instrumented method.

[srikanthccv]

We appreciate all contributions. It's unfortunate if it came across as rude. It wasn't the intention to "overrule".

Here is our POV; with hundreds of issues in the backlog (nobody has time for a contrib repo), it's unrealistic to independently every issue to see if it's still relevant after dozen new releases and what parts are already solved or fixed. There were many similar issues about spec compliance with slight variations. Your issue had the linked PR, which seemed to address the part of it. The instrumentation version described is far behind, and we don't run es7 on CI and haven't decided what to do. It has often helped us close the old ones and ask for help. Simply copying the old text won't be much helpful because we are going to verify anyways what's missing as of today and devise a plan. And leaving behind many issues with the same goal won't make project management easy.