Oleksandr Gorokhovskyi

> The GMP exporter relies primarily on [service.name, service.namespace, and service.instance.id](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource/semantic_conventions#service) (mapped to job and instance in the [prometheus_target](https://cloud.google.com/monitoring/api/resources#tag_prometheus_target)). Interesting.. I am using [otlp receiver](https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver) together with `resourcedetection` processor (same...

``` cat fileexporter.json | jq -s '.[0].resourceMetrics[0].resource' { "attributes": [ { "key": "testattr", "value": { "intValue": "7357" } }, { "key": "host.hostname", "value": { "stringValue": "redacted" } }, { "key":...

Thanks, it worked. A small note - I had to specify `action` eg: ``` processors: resource: attributes: - key: service.instance.id from_attribute: host.name action: insert ``` Looking forward to `resourcetotelemetry` support!

Maybe someone will find this usefull. After playing with `resourcetotelemetry` feature (added to a forked version of the collector) I realized that it wasn't what I need - most of...

Interface.TaggedVlans is another one

After further investigation, looks like the problem is in `tagged_vlans` and not `link_peers` as I assumed previously.. so the issue is not the same as #151 but of similar nature....

~~Same with the `asns` property of Site - spec seems to be correct, but no the generated code.~~

The root issue https://github.com/netbox-community/netbox/issues/15404 The spec generated via `{netbox_url}/api/schema` (eg https://demo.netbox.dev/api/schema) is indeed incorrect.

Switching from DHCP to static and back resolved the issue. During the process, I changed the IP, which might have also played a part.