Charts
10 results found
-
Add more specific roles for Charts
It will be great to have more specific roles to Charts totally separate from other Altas roles.
Currently if you want to have one team member allowed to configure charts,
you have to give him access (at least read only) to everything outside of Charts space, as cluster and database informations or even Stitch configuration.61 votesHi everyone,
We have some exciting news for you all, we are commencing work on Charts specific roles this month!
We will be launching the following x2 new roles:
Charts Author - these users can view/create charts and dashboards in Charts as long as they have access to the underlying data sources.
Charts Viewer - these users can view charts and dashboards in Charts as long as they have access to the underlying data sources
Both roles will have reduced permissions at the Project level and will have access to only Charts resources.
This is expected to go live in Q1 of next year.
Thanks
Emma
-
Ability to toggle Dark Theme
Most dashboards from different services offer the ability to be in Dark Mode, which is easier to read and saves loads of energy.
As a workaround users can use browser extensions to apply a css dark theme.
Firefox: https://addons.mozilla.org/en-US/firefox/addon/dark-mode-webextension/
Chrome: https://chrome.google.com/webstore/detail/care-your-eyes/fidmpnedniahpnkeomejhnepmbdamlhl
39 votesWe are planning to start work on a Dark mode in Charts in the first half of next year.
-
Hyperlinks in charts
The idea is to be able to create hyperlinks with data from the charts in order to create connections with other web apps. This is similar to a Kibana functionality
26 votes -
Switching Chart Type should not erase existing settings
If I change the chart type (e.g. a Line Chart) from Discrete to Continuous, it'd be nice if I didn't have to restart from scratch. Currently it erases my settings.
24 votes -
Chart zoom
Horizontally dragging across a section of a chart with your mouse should zoom in on the range of data you selected. Default zoom ranges would also be nice (ex: a chart with lots of historical data, but only displaying the last n-days, allowing a user to optionally zoom out to see the rest of the data).
17 votes -
Custom color scheme
I would like to have the ability to define my own color scheme that is then used for either entire dashboards or individual charts. At the current moment, the color schemes available are hardcoded. While they make the dashboards attractive, when integrated into existing applications that follow a certain styleguide, it's not ideal.
15 votesThanks for the suggestion Thomas – we are planning on implementing this later this year.
-
Allow to customize/substitute mongodb logo on publicly shared dashboard
As described, it would be nice to have publicly shared dashboard to have own logo or hide the existing mongodb logo(just like embedded chart).
11 votes -
lowlevel data api
Mongodb-charts is great but still lacking a lot of features (which is not super surprising given it's age). To work around mobile issues, missing zoom, server side rendering and similar it would be great if the sdk exposed a low level data endpoint so that we can create our own visualizations on top of the aggregated & cached data from mongodb charts.
I imagine sth like:
const sdk = new ChartsEmbedSDK({
baseUrl,
});
const data = await sdk.getData({chartId})
unrelated side note: it would be great if the embed sdk was open source so that we can just contribute little enhancements…
3 votes -
Add inclusive option for relative date filter
Using a relative filter "from last 1 year" displays the last 365 days of data. If the dates are binned by month, that often means that the first month does not contain a full month's data.
Please add an option for the relative filter to include complete data for the first bin.
1 vote -
Do not allow same item to be added to data sources
We are seeing that we will have the same data source added multiple times.
This is confusing to the end user1 voteThanks Scott. We currently allow this because it’s possible the user would want to have multiple data sources pointing to the same collection, but with different data source pipelines.
That said I agree 100% that it’s confusing, and we have some plans to rework data sources to avoid this situation.
- Don't see your idea?