Perhaps prometheus remote write exporter should map resource attributes

[morigs]

Currently, prometheusremotewrite exporter looks at resource attributes and if there are job and label attributes they are mapped to the corresponding Prometheus labels. But the rest of the resource attributes are ignored.
This provides a bad user experience because users have to add job and instance attributes together with semantic attributes.
Thus I have to duplicate my service.name to the job and service.instance.id to the instance.

I think it was quite useful if the prometheusremotewrite exporter checked the attributes and, if the value of some of the attributes (job or instance) is missing, would use the default value of the corresponding semantic attribute (service.name or service.instance.id respectively).

It would also be nice to map all of the resource labels to Prometheus metric labels.

Is there any points on this in the spec? What does Prometheus WG think about this?

[bogdandrutu]

/cc @rakyll @dashpole @alolita