You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: