[Windows] Add dimension fields for service datastream to support TSDB.

[ritalwar]

• Enhancement

What does this PR do?

This PR adds dimension fields for service datastream to support TSDB enablement.

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.

Related issues

• Relates Windows TSDB Enablement #6993

[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: 2023-08-28T09:48:09.707+0000

• Duration: 20 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	150
Skipped	0
Total	150

🤖 GitHub comments

Expand to view the 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% (8/8)	💚
Files	91.667% (11/12)	👍
Classes	91.667% (11/12)	👍
Methods	85.156% (109/128)	👍
Lines	92.459% (5726/6193)	👍
Conditionals	100.0% (0/0)	💚

[agithomas]

@ritalwar , there exist only one field - uptime.ms having a metric value. Is there merit in doing TSDB enablement for this datastream?

cc @lalit-satapathy

[lalit-satapathy]

@ritalwar , there exist only one field - uptime.ms having a metric value. Is there merit in doing TSDB enablement for this datastream?

cc @lalit-satapathy

Single field metric document is fine. What metric type is uptime.ms? @ritalwar Can you share a sample service data stream document below?

[ritalwar]

@ritalwar , there exist only one field - uptime.ms having a metric value. Is there merit in doing TSDB enablement for this datastream?
cc @lalit-satapathy

Single field metric document is fine. What metric type is uptime.ms? @ritalwar Can you share a sample service data stream document below?

uptime is the time duration since the service was last started, and uptime.ms is the service's uptime specified in milliseconds.

Here is the sample doc:

{
    "data_stream": {
      "dataset": "windows.service",
      "namespace": "default",
      "type": "metrics"
    },
    "service": {
      "type": "windows"
    },
    "windows": {
      "service": {
        "display_name": "Distributed Transaction Coordinator",
        "id": "-VO2Lm89v4",
        "name": "MSDTC",
        "path_name": "C:\\Windows\\System32\\msdtc.exe",
        "pid": 11592,
        "start_name": "NT AUTHORITY\\NetworkService",
        "start_type": "Automatic (Delayed)",
        "state": "Running",
        "uptime": {
          "ms": 767641828
        }
      }
    }
  }

[agithomas]

LGTM!

[lalit-satapathy]

Single field metric document is fine. What metric type is uptime.ms? @ritalwar Can you share a sample service data stream document below?

What metric type for uptime.ms?
gauge, shall I make this metric_type change in the same PR?

[harnish-elastic]

@ritalwar, I have performed the TSDB-enablement-test-kit with this PR (including the metric_type field changes). The package is working fine. LGTM!

[elasticmachine]

Package windows - 1.34.0 containing this change is available at https://epr.elastic.co/search?package=windows