Core labels
All Ryvn-managed resources include the following labels:Using labels for observability
Setryvn.app/telemetry-destination on the Pod for logs and on the Service
for application scrape metrics. Its value is the source assignment’s Workload
destination alias: an exact, case-sensitive Kubernetes label value, unique within
the consuming environment even for unavailable connections. Other environments
can reuse it.
--alias defaults new assignments to the connection name; repeated creates
preserve custom aliases. Creating with a different alias requires an explicit update.
You can also edit aliases in Settings → Connections → Observability → Telemetry
connections. Update workload labels when renaming an alias.
Missing, empty, default, and unknown labels use the selected default connection.
Removing an assignment sends future telemetry using its old alias to the default.
Assigned but unavailable aliases do not fall back. Some system-level node information
is sent to every assigned connection regardless of workload labels.
Example: filtering by release version
If you have access to your Kubernetes cluster, you can use theryvn.app/release-version label to find all resources
running a specific version:
Example: monitoring version distribution
You can use these labels to monitor the distribution of versions across your environments, which is particularly useful during rolling updates:my-api service along with their labels, including which version each pod is running.
Integration with external tools
Many observability tools support Kubernetes label-based filtering and grouping:- Prometheus: Use label selectors in your scrape configurations
- Grafana: Create dashboards that filter metrics by service and version
- Datadog: Filter and group resources by Kubernetes labels
- New Relic: Use labels for filtering and creating custom views
The specific labels available may vary slightly depending on the service type (Server, Job, Chart, or Terraform).