search

elastic / beats

:tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash
https://www.elastic.co/products/beats
Other
12.06k stars 4.89k forks source link

Issue with Metricbeat "Database selector [Metricbeat MSSQL] ECS" Visualization #18659

Closed MakoWish closed 8 months ago

MakoWish commented 4 years ago

Kibana version: 7.3.0

Elasticsearch version: 7.3.0

Server OS version: Ubuntu 19.04 disco

Browser version: Google Chrome Version 75.0.3770.100 (Official Build) (64-bit)

Browser OS version: Microsoft Windows 10 Enterprise Version 1903

Original install method (e.g. download page, yum, from source, etc.): Debian Package

Description of the problem including expected versus actual behavior: The "Database selector [Metricbeat MSSQL] ECS" visualization included with Metricbeat dashboards does not recognize the field "mssql.database.name". I can confirm in both Discover and the metricbeat-* index pattern that the field does exist, and there are tons of records with data in the field.

Steps to reproduce:

  1. Install dashboards using "metricbeat.exe setup"
  2. View "Database selector [Metricbeat MSSQL] ECS" visualization
  3. Attempt to click on the selector

Errors in browser console (if relevant): "Filtering occurs on the "mssql.database.name" field, which doesn't exist on any documents in the "metricbeat-*" index pattern. Choose a different field or index documents that contain values for this field."

Provide logs and/or server output (if relevant):

elasticmachine commented 4 years ago

Pinging @elastic/beats

louraider commented 4 years ago

Have same problems from windows mssql

MakoWish commented 4 years ago

This seems to have been fixed in 7.4.0. Works for me after upgrading.

louraider commented 4 years ago

This seems to have been fixed in 7.4.0. Works for me after upgrading.

i'm using 7.4 and it's didn't worked

yaronmil commented 4 years ago

is there any solution ?

louraider commented 4 years ago

is there any solution ?

Didn't find

MakoWish commented 4 years ago

The selector actually works for me in 7.4, but it does not follow the filter. If I set the filter for only records containing (for instance) "vsphere.host.name: *", it will show those records, but it will also show records that do not contain the field. My original issue seems to have been resolved in 7.4, but this visualization still does not work as expected.

JalehD commented 4 years ago

version 7.5 still affected but this issue.

elasticmachine commented 4 years ago

Pinging @elastic/integrations-services (Team:Services)

MakoWish commented 3 years ago

Any update on this? Issue has been open for nearly a year and is still present on 7.8.0.

sayden commented 3 years ago

Can you open an ER / Bugfix request in Beats GH? That's the reason why we haven't come up to fix this yet. Thanks! Contributions welcome :slightly_smiling_face:

MakoWish commented 3 years ago

I don't believe this is a Beats issue. This is a Kibana visualization issue.

fabinho1314 commented 3 years ago

Any news regarding this matter?

I also cannot select any DB in the Database selector [Metricbeat MSSQL] ECS mssql.database.name

insu0929 commented 3 years ago

Using both Kibana, MetricBeat version 7.12, with MSSQL Server on Windows system. Facing the same issue here... Any updates??

botelastic[bot] commented 2 years ago

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

MakoWish commented 2 years ago

A simple comment with a nice emoji. 👍

botelastic[bot] commented 1 year ago

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!