Skip to content

OTEL data plane collector metric persistence #17

@Bobi-Wan

Description

@Bobi-Wan

How to categorize this topic?

/area observability
/area monitoring
/kind enhancement
/kind poc

/label teamsize/small

What is the topic about?:
Currently, an OTEL collector is being developed for shoot data planes, which will serve 2 purposes.

  1. metric filtering in the data plane for network traffic reduction
  2. metric retention when network connectivity between control and data planes is failing.

This tasks is to create a POC for the second point. A general idea is to use the already existing OTEL collector pipelines and add a processor/extractor that has the option for metric retention. The goal is a moving target, but initially, being able to retain metrics for 10-15 minutes would be a win, as network connectivity issues don't usually persist for too long and this would be useful for stakeholders.

Metadata

Metadata

Labels

area/monitoringMonitoring (including availability monitoring and alerting) relatedkind/enhancementEnhancement, improvement, extensionkind/pocProof of concept or prototypelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.os/garden-linuxRelated to Garden Linux OSteamsize/smallA team of 1-2 people.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions