[Kubernetest OTEL] Follow up enhancements

[tetianakravchenko]

Proposed commit message

Please explain:

• WHAT:
  • change logo
  • fix package description
  • add consistency to the terminology: usage vs utilisation, remove pct
  • do not rely on generic.otel datastream name: changed to filter data_stream.dataset: *.otel, use metrics-*otel* for adhoc dataviews, for events use logs-*otel*
• WHY: Address review comments of the first version of the kubernetes content package

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[tetianakravchenko]

Hey @ChrsMark in this PR I think I've addressed your comments you've left in #10910 (review), mainly in the second commit - 071f1ef

Could we try to be consistent with the terminology, i.e. usage vs utilization vs pct? Our panel titles etc should be aligned with the semantic convention definitions. Hence we should only use usage or utilization where it applies (no need for pct, utilization is a ratio anyways).

1. chnged name of those vizualisation to Usage

2. for Node overview vizualisations switched to utilization and changed formula for cpu to address [Draft] K8s otel overview dashboard #10910 (comment)

Could we consider leveraging the limits' utilization metrics as well? There was strong push-back by the community when we introduced the *.node.utilization metrics so relying only these might be risky in case the community decides to deprecate them. From my perspective these are nice to haves but we can rely to *.cpu.usage ones and the limit based utilizations.

to double-check: is this comment already updated? Now there is used both:

Also in the panels it would be nice if we explicitly mention what utilization we display (ratio against the node's capacity VS ratio against the limits).

done

[gizas]

Just a reminder to update the id of the dashborad :kubernetes-opentelemetry-cluster-overview

[ChrsMark]

Thank's for addressing the comments!
LGTM

[ChrsMark]

FYI there is a plan to add back the k8s.node.cpu.utilization but it will take some time since it's happening through a deprecation process which will take a while. In that case the k8s.node.cpu.utilization will be a ratio against the Node's capacity not the Node's allocatable cpu (capacity>allocatable), but it can be decided later if it will be fine to switch to that metric directly or not.

[tetianakravchenko]

@gizas

Just a reminder to update the id of the dashborad :kubernetes-opentelemetry-cluster-overview

Note: the name of the dashboard must follow this pattern: https://github.com/elastic/package-spec/blob/v3.2.2/spec/content/kibana/spec.yml#L12, so renamed to kubernetes_otel-cluster-overview
82c295a

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
99.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 82c295a

History

• 💚 Build #16723 succeeded 64d6c99

[elastic-vault-github-plugin-prod]

Package kubernetes_otel - 0.0.2 containing this change is available at https://epr.elastic.co/search?package=kubernetes_otel