Update temporal integration to support temporal version 1.27

[phuongdnguyen]

What does this PR do?

• Update generate_metadata script to adapt with metrics definition metric_defs.go defined in multiple lines in temporal 1.27
• Update tests

Motivation

Temporal integration is outdated. Current integration support temporal server 1.19, the latest version is 1.27. While we can include missing metrics in extra_metrics section, i think it's better to keep the integration up to date so users can use the agent without any more configurations.
Currently, the diff between list of metrics this integration support and the latest major version of temporal is already quite large, around 70 metrics.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.49%. Comparing base (09056ae) to head (193f06e).

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
confluent_platform	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
presto	?
solr	?
temporal	100.00% <ø> (ø)
tomcat	?
weblogic	?

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[phuongdnguyen]

Hi @Kyle-Neale , sorry for the direct ping but i see you're approver of temporal integration before. Can you kindly take a look?

[phuongdnguyen]

Not sure why the ci is complaining about missing ACTIONS_ID_TOKEN_REQUEST_URL

[janine-c]

The docs team is only responsible for the metadata file, but it looks fine to me :)

[iliakur]

Thanks for the contribution and apologies for the delayed response.

I noticed we're dropping support for Temporal v1. Do you mind undoing those changes please? We'd like to support customers who are monitoring older versions of Temporal too.

[phuongdnguyen]

Hi @iliakur , not sure if i'm following.
In general, i think a new version of temporal (with metrics change) should have a corresponding version of DataDog agent. What is our strategy to do it here? Are we saying that because we want to support customer running older version of temporal, hence we won't update the temporal integration, which also mean that we won't support customer running newer version of temporal?

[iliakur]

Hi @iliakur , not sure if i'm following. In general, i think a new version of temporal (with metrics change) should have a corresponding version of DataDog agent. What is our strategy to do it here? Are we saying that because we want to support customer running older version of temporal, hence we won't update the temporal integration, which also mean that we won't support customer running newer version of temporal?

@phuongdnguyen we want any given agent version to support both versions of Temporal.

Say you're a customer who wants to upgrade your Datadog Agent, but (for whatever reason) cannot update your Temporal deployment. You'd be pissed if you're blocked from upgrading your agent, right?

[phuongdnguyen]

Hi @iliakur , in that case, perhaps what we might want to do is just accumulate all metrics supported through all version of Temporal. Are there any limit cause it sounds not too efficient 🤔

[iliakur]

In files like metadata.csv we definitely keep all the metrics. If you want, you can add notes to descriptions saying which versions of temporal a given metric comes from.

Figuring out which metrics to collect efficiently is a question of implementation. Let me know if you want concrete tips for that.

[phuongdnguyen]

@iliakur Thanks, understood your concerns now, will make updates to the patch 👍

[phuongdnguyen]

Hi @iliakur, can take a look at #20469, much appreciated 🙇.
I'm going to split this PR into 2 PR, the first is 20469, update the script to generate metadata.
The second PR following that will patch the METRIC_MAP & tests to up to date with temporal latest version

[iliakur]

Hi @iliakur, can take a look at #20469, much appreciated 🙇. I'm going to split this PR into 2 PR, the first is 20469, update the script to generate metadata. The second PR following that will patch the METRIC_MAP & tests to up to date with temporal latest version

@phuongdnguyen done! left some suggestions.