windowsservicereceiver wireframe

[shalper2]

Description

Create a metric receiver to relay the status of a Windows Service. This is a wireframe for the receiver to be implemented.

Link to tracking issue

Fixes 31377

Testing

None

Documentation

Basic documentation has been written/generated by mdatagen.

[dehaansa]

What's the difference between this and #35362 ?

[shalper2]

the level of implementation. the first one turned into an actual component which was out of scope for the original PR.

[pjanotti]

Sorry for the delay @shalper2 - various minor suggestions.

If you give rights to push to your branch I can help resolving things like https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/13312274770/job/37177669827#step:8:376

[atoulme]

changes lgtm, can't speak to the windows specific knowledge though. @pjanotti please review and approve as additional codeowner.

[pjanotti]

LGTM @atoulme

[dehaansa]

Is this metric name right? Shouldn't it be windows.service.status? I'd be partial to dropping the windows prefix from it & the attributes but that's just my preference, I think the name not having status feels incorrect.

[pjanotti]

I like the idea of adding status. The windows.service prefix on the metric name seems reasonable since the metric is specific to Windows Services. However, it becomes redundant to add windows.service to the attributes, just name and startup_mode seems reasonable.

[pjanotti]

Metric and attributes renamed per above comment d1e0072