elastic / elastic/integrations
[Apache] Update dashboard data view
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
Description
In Apache integration package, found that if the visualization is having a data type conflicted field, user can either get a warning/error.
This issue can occur with any two integrations having a particular field and different data type and querying either `logs-*` or `metrics-*` data views. This issue would not have occurred if the data type of these fields would have been consistent across data streams.
I have tested two scenarios here.
I have ingested mock data with other logs data stream and with keyword data type for `http.response.status_code` data stream. Now I when I go to the dashboard, I can see warning message for none apache data stream.
Now I have changed the visualization data view from `logs-*` to `logs-apache.*` and I can see the warning is vanished. This data view change across the dashboard could resolve the current issue.
Please refer to the attached screenshots.
Both visualizations are having warning messages.

Different data streams warning message in Apache dashboard even if the dashboard is having `data_stream.dataset: apache.access` filter. (This is just a mock data that I have ingested with other package)

Updated data view for one visualization and warning message is vanished.

**Note: This can happen for other integrations dashboard as well in case field mapping is not correctly done**
Contributor guide
Assessment
This issue has not been assessed yet.