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
When I run app simulator with the k8s generator and deploy my services to k8s, I can not easily identify the language used for a service using kubectl or other kubernetes tooling. This would especially come handy if I want to apply automatic instrumentation based on annotations with the otel operator
Proposed Solution
I suggest that we add a few more labels to the services, i.e.
app.kubernetes.io/component (from the recommended labels) with value database, service, loader, etc, such that my instrumentation only aims at services
app-simulator.io/type with the type attribute from our config java
Later on we can decide to add more attributes into labels (or annotations), but I think those 2 are important to be added to enable some more features.
Problem Statement
When I run app simulator with the k8s generator and deploy my services to k8s, I can not easily identify the language used for a service using kubectl or other kubernetes tooling. This would especially come handy if I want to apply automatic instrumentation based on annotations with the otel operator
Proposed Solution
I suggest that we add a few more labels to the services, i.e.
app.kubernetes.io/component
(from the recommended labels) with valuedatabase
,service
,loader
, etc, such that my instrumentation only aims at servicesapp-simulator.io/type
with the type attribute from our configjava
Later on we can decide to add more attributes into labels (or annotations), but I think those 2 are important to be added to enable some more features.
Alternatives Considered
No response
Additional Context
No response
Checklist
The text was updated successfully, but these errors were encountered: