add directory attribute in file.count metric (filestats receiver)

[josepcorrea]

Component(s)

receiver/filestats

Is your feature request related to a problem? Please describe.

when you want to count the files in a directory, the metric does not show the directory name, so you cannot distinguish different receivers.

 filestats/1:
   include: /tmp/test1/test*
   metrics:
     file.count:
       enabled: true
   resource_attributes:
     file.path:
       enabled: true

 filestats/2:
   include: /tmp/test2/*
   metrics:
     file.count:
       enabled: true
   resource_attributes:
     file.path:
       enabled: true

Only one metric is generated, so you cannot distinguish between the two:

file_count{host_name="localhost", os_type="linux"}

Describe the solution you'd like

Add the directory attribute to be able to distinguish the different file_count metrics:

file_count{directory="/tmp/test1", host_name="localhost", os_type="linux"}
file_count{directory="/tmp/test2", host_name="localhost", os_type="linux"}

In this way the metrics of both directories can be distinguished.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/filestats: @atoulme

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[atoulme]

The file path should be present as a resource attribute. The filestatsreceiver doesn't set the host_name and os_type attributes.

Please see this file for what the receiver generates: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/filestatsreceiver/testdata/integration/expected.yaml

[josepcorrea]

Thanks @atoulme :

Is there a way to display the path directory?

The attributes host_name and os_type are added with processing resourcedetection component like this:

resourcedetection/system:
detectors: ["system"]
system:
hostname_sources: ["os"]
resource_attributes:
host.name:
enabled: true

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/filestats: @atoulme

See Adding Labels via Comments if you do not have permissions to add labels yourself.