Specifying supported Metrics for Embrace integration

[scottieb3]

What does this PR do?

Updating the metadata for Metrics supported in the Embrace integration

Motivation

Following guidance from Datadog Tech Partnerships team

Review checklist

• [ ✅ ] PR has a meaningful title or PR has the no-changelog label attached
• [ ➖] Feature or bugfix has tests
• Git history is clean
• [ ➖ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
• [ ➖] If this PR includes a log pipeline, please add a description describing the remappers and processors.

Additional Notes

Anything else we should know when reviewing?

[scottieb3]

@davidlawrencer

[scottieb3]

@mfrishert

[scottieb3]

updated based on Datadog's response to open questions (via email)

[scottieb3]

@davidlawrencer + @mfrishert ( @jschoijet ): anything obvious I'm missing before I ping our Datadog contacts?
It keeps failing on the csv, but I'm following docs (here )

[jschoijet]

@davidlawrencer + @mfrishert ( @jschoijet ): anything obvious I'm missing before I ping our Datadog contacts? It keeps failing on the csv, but I'm following docs (here )

It’s confusing. Looks like It’s failing because service_checks expects a metadata_path:

"service_checks": {
        "metadata_path": "assets/service_checks.json"
 }

But according to docs it can be {}. Try changing it to the code I mentioned. But worth to check with them