Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor Prometheus metrics storage #9921

Closed
exekias opened this issue Jan 7, 2019 · 1 comment · Fixed by #9948
Closed

Refactor Prometheus metrics storage #9921

exekias opened this issue Jan 7, 2019 · 1 comment · Fixed by #9948
Assignees
Labels
enhancement Metricbeat Metricbeat Team:Integrations Label for the Integrations team v7.0.0-beta1

Comments

@exekias
Copy link
Contributor

exekias commented Jan 7, 2019

Prometheus module stores metrics structured in Elasticsearch documents, but current approach has some issues:

  • It needs user defined mapping, or use automatic mapping for fields
  • Namespace key is introduced to avoid mapping issues between different instances, but that leads to more fields (mapping explosion)

We should come up with a new way to store Prometheus metrics that fixes these issues.

@exekias exekias added enhancement Metricbeat Metricbeat Team:Integrations Label for the Integrations team labels Jan 7, 2019
@exekias exekias self-assigned this Jan 7, 2019
@exekias
Copy link
Contributor Author

exekias commented Jan 7, 2019

I've started a few experiments around this, will come up with a proposal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Metricbeat Metricbeat Team:Integrations Label for the Integrations team v7.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant