Skip to content

[Meta] [TSDB] Eliminate fingerprinting of dimensions and labels added as part of TSDB Enablement #9910

@agithomas

Description

@agithomas

The Elasticsearch issues

These changes help to overcome the dimension limit and the need to hashing the labels and dimensions that are part of the Elastic Integration package fields.

The changes are presently evaluated & tested for the Prometheus package.

This meta issue captures the scope of the integration package (datasets) which could take the benefit of above mentioned improvements added to Elasticsearch.

Requirements

  • 8.14 or above.

Related Issues

Pass Criteria

  • No document drop should happen after applying the changes

Testing Methodology.

### Applicable Integration package list.
- [ ] AWS/cloudwatch_metrics
- [ ] azure_application_insights
- [ ] azure_metrics/monitor
- [ ] elasticsearch/ingest_pipeline
- [ ] etcd/metrics
- [ ] gcp/cloudrun_metrics
- [ ] gcp/cloudsql_mysql
- [ ] gcp/cloudsql_postgresql
- [ ] gcp/cloudsql_sqlserver
- [ ] gcp/compute
- [ ] gcp/dataproc
- [ ] gcp/gke
- [ ] gcp/loadbalancing_metrics
- [ ] gcp/pubsub
- [ ] gcp/redis
- [ ] gcp/storage
- [ ] istio/istiod_metrics
- [ ] istio/proxy_metrics
- [ ] microsoft_sqlserver/transaction_log
- [ ] mysql/performance
- [ ] oracle/performance
- [ ] postgresql/activity
- [ ] prometheus/collector : https://github.com/elastic/integrations/pull/9785
- [ ] prometheus/query : https://github.com/elastic/integrations/pull/9785
- [ ] prometheus/remote_write : https://github.com/elastic/integrations/pull/9785
### Update Developer Guidelines Document
- [ ] TSDB Guidelines document (github)
- [ ] Developer Documentation Page (if applicable)

Metadata

Metadata

Assignees

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