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

Generate fields.yml from prometheus response #3

Closed
wants to merge 1 commit into from

Conversation

jsoriano
Copy link
Owner

Parse prometheus response and generate fields for metricbeat light modules.

Questions:

  • Do we want something like this?
  • It adds hundreds of fields, and we already have the prometheus.metrics.* dynamic mapping, do we want to generate documentation only and not fields?

@jsoriano jsoriano self-assigned this Jun 26, 2019
@exekias
Copy link

exekias commented Jun 27, 2019

I think It's great to have docs for all fields, specially if they come for free. As you say, we don't really need the mappings though.

How about doing exactly what's on this PR but add a flag to fields.yml to explicitly say that the field should not end up in mapping?, Something like docs_only for instance

@jsoriano jsoriano closed this Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants