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

Metrics being seen im logs-* in Kibana if filebeat input is used to retrieve metrics #2208

Open
ishleenk17 opened this issue Jan 31, 2023 · 1 comment
Labels
bug Something isn't working Team:Elastic-Agent Label for the Agent team

Comments

@ishleenk17
Copy link

There is a usecase where the filebeat input (say httpjson) is being used to get metrics in integrations.
Since httpjson is a filebeat input the metrics are seen under logs-*.

The expectation is to get the metrics in the metrics-* even if we use filebeat input.

If we try to change the data_stream.type to "metrics", that causes a mismatch with the index type.

213635682-cc150976-8dd9-4478-ad2a-a3dd4a9f661f

@ishleenk17 ishleenk17 added the bug Something isn't working label Jan 31, 2023
@ishleenk17 ishleenk17 changed the title Metrics going to logs-* if filebeat input is used to retrieve metrics Metrics being seen im logs-* in Kibana if filebeat input is used to retrieve metrics Jan 31, 2023
@cmacknz
Copy link
Member

cmacknz commented Jan 31, 2023

The filebeat default for logs is correct, this is a side effect of us using Filebeat as generalized runner for inputs beyond just logs because it is convenient.

If we try to change the data_stream.type to "metrics", that causes a mismatch with the index type.

How did you try to do this? Are their agent diagnostics you can attach while this error is happening? If you changed the datastream.type in the agent policy Filebeat should respect it. This error looks like the index is still set to log-golang.expvar-default instead of metrics-golang.expvar-default.

The first problem here will be getting Filebeat to target the correct index. The second step will be ensuring that the index permissions API key generated by Fleet also targets the correct index but it looks like we haven't gotten to that point yet.

@cmacknz cmacknz removed their assignment Jan 31, 2023
@cmacknz cmacknz added the Team:Elastic-Agent Label for the Agent team label Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

No branches or pull requests

2 participants