You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From other services in the App O11y plugin, I see that they report many resource attributes that we don't, and they could be useful e.g. to differentiate between instances:
host.name
os.description
os.type
process.command_args
process.executable.name
process.executable.path
process.owner
process.pid
process.runtime.description (e.g. go version go1.19.2 linux/amd64)
process.runtime.name
service.instance.id
service.namespace
telemetry.sdk.language
telemetry.sdk.name
telemetry.sdk.version
If we detect that the process runs in a container:
container.id
If we detect that the process runs in K8s:
k8s.node.name
k8s.pod.name
k8s.namespace.name
For Kubernetes, the easiest way would be to just allow setting these values via env vars, then use the valueFrom clause in the deployment descriptors.
The text was updated successfully, but these errors were encountered:
From other services in the App O11y plugin, I see that they report many resource attributes that we don't, and they could be useful e.g. to differentiate between instances:
host.name
os.description
os.type
process.command_args
process.executable.name
process.executable.path
process.owner
process.pid
process.runtime.description
(e.g.go version go1.19.2 linux/amd64
)process.runtime.name
service.instance.id
service.namespace
telemetry.sdk.language
telemetry.sdk.name
telemetry.sdk.version
If we detect that the process runs in a container:
container.id
If we detect that the process runs in K8s:
k8s.node.name
k8s.pod.name
k8s.namespace.name
For Kubernetes, the easiest way would be to just allow setting these values via env vars, then use the
valueFrom
clause in the deployment descriptors.The text was updated successfully, but these errors were encountered: