Update Elastic Package Registry integration to use new indexer metrics (get operations)

[mrodm]

What does this PR do?

This PR updates the Elastic Package Registry integration to take into account the new metrics related to get operations (duration histograms) from elastic/package-registry#853.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• Updated metrics are retrieved and shown in the dashboard
• Update docker tag to be used in tests (_dev/deploy/docker/Dockerfile)

How to test this PR locally

1. Go to packages/elastic_package_registry and build the package (elastic-package build).
2. Boot up the Elastic stack using elastic-package from packages/elastic_package_registry folder.
3. Boot up the EPR service by using the command: elastic-package service up -v inside the packages/elastic_package_registry folder
4. Get the container name to be used in configuration. It should be something similar to: elastic-package-service_elastic_package_registry_1
5. Add EPR integration in Kibana:
   • Set as hosts: http://elastic-package-service_elastic_package_registry_1:9100
   • Go to Discover and check in metrics-*. It can be filtered by:
     • service.type: elastic_package_registry
     • data_stream.dataset: elastic_package_registry.metrics
6. You can run queries against the EPR service:
   • Check the exposed container locally using docker ps

      $ docker ps |grep elastic-package-service_elastic_package_registry
     eacd95c89dc3   elastic-package-service_elastic_package_registry       "./package-registry"     About a minute ago   Up About a minute (healthy)   8080/tcp, 0.0.0.0:53910->8081/tcp, 0.0.0.0:53911->9110/tcp   elastic-package-service_elastic_package_registry_1

   • Run curl commands to that port, in this example the port is 53910:

     curl -s http://localhost:53910/
     curl -s http://localhost:53910/health
     curl -s http://localhost:53910/search?prerelease=true
     ... 

Related issues

• Relates package-registry observability integration package-registry#797

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-07-28T17:22:35.860+0000

• Duration: 16 min 41 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5
Skipped	0
Total	5

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚 2.868
Classes	100.0% (1/1)	💚 2.868
Methods	100.0% (8/8)	💚 10.749
Lines	100.0% (77/77)	💚 9.399
Conditionals	100.0% (0/0)	💚

[mrodm]

To be updated with a newer tag of a new package-registry release containing this PR elastic/package-registry#853.

[mrodm]

Currently , there will be just one metric (get_duration_seconds) in this indexer group. It seems to me that it could make sense to have that group even that.

WDYT?

These are the current groups defined:

• package_registry.http
• package_registry.labels
• package_registry.indexer
• package_registry.storage_indexer

[mtojek]

nit: maybe drop a comment on why exactly is this SHA needed.

[mrodm]

Ok! I'll do that, and in following PR, I'll set the the newer tag of the package registry
Thanks!

[mrodm]

At the end, there has been a package-registry release, so no need to use the SHA. I'll update it to v1.11.0