wallingfordce
Data Pipeline
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: The "Maximum number of series (50) exceeded" warning, reword it, make it sticky, and document it.
Thanks for responding! I can appreciate having the option to expand the included data set, but this feedback is less about working around the limit and more about always displaying the message, rewording the message, and documenting the limitation.Do you get booted out of Support case drafts?
I would like to see the Support Portal not auto-refresh auto-log-me-out while I'm working in there. I too often get booted out of drafts of support tickets by being auto-ejected and logged out of the support portal and community site. I'm just actively typing along in the Case Comments box, and the page refreshes and I'm logged out, losing all my work in the process. Of course, this is my reminder to stop using the Support Portal UI for drafting my comments, but it's so tempting to just work the way I expect to be able to work, and then I forget and get burned.Enhance Usage Model to include segmentation of Email Subscription vs Front-End queries
When analyzing dashboard and widget query performance, I would like to be able to focus on only front-end user queries, or just on email subscriptions, or both. Unfortunately, the source data of the Usage Analytics Model does not contain information that allows us to distinguish whether a dashboard was executed via the Web UI or through a scheduled job. Therefore, we are unable to perform the requested analysis.Who's doing multitenancy?!
Referencing this table of tenant segregation levels, we have been doing the Internal Capabilities approach for 8 years (user groups and JWT with our own SSO router which predates the one in the marketplace). We recently migrated from Windows to Linux and would like to find a way for our staff to manage the Sisense environment via SSO using Entra ID. We're building an intermediate solution but are also considering Sisense Tenants. We assume, without having done a POC, that we'll be able to configure the system tenant to use Entra, while configuring the tenants to use the JWT we're currently using. We are drawn to allowing our clients to use the All Dashboards feature within their tenant. We will supress their access to White Labelling and SSO. We use Live Models, not Elasticubes. We expect some positive feedback on clients having some access to review their data models as well. We realize that we have to migrate our clients into the Sisense Tenants if we go that route. My question for YOU then... If you use Sisense Tenants, how's it going? What's your scenario and how has this feature supported you? Has it let you down in any way? If you don't use Sisense Tenants, why not? Is there something to your multitenancy that Tenants doesn't support (e.g. Report Manager)? Any other thoughts, advice or feedback... things I should consider and questions I should be asking? Thanks in advance!Hide the "Every ElastiCube update" option on Live Models.
When using a Live Model data source, Pulse Alerts UI changes to reflect this, showing an option for the alert frequency, which only appears when the data source is a Live Model. For a dashboard subscription, the UI does not change with the option for "Every ElastiCube update" being present and seeming to be selectable, though it is not. Please hide this option when the primary data source on a dashboard is a Live Model. Optionally, you could look into hiding only when all widgets on the dashboard use a Live data source and none use an EC data source.Add email operations to the Audit Logs
In an effort to simplify our troubleshooting of email issues, I would like to see email operations added into the Audit Logs. That enhancement, coupled with others like Make the time scope of Generate a Log File configurable | Sisense Community and Access various logs from Sisense UI under file management option | Sisense Community could greatly enhance our ability to support ourselves and reduce our support ticket submissions.Make the time scope of Generate a Log File configurable
We often need to troubleshoot an issue that wasn't reported to us within the 10-hour time frame covered by the Generating Support Log Files feature. We'd like to see the scope of time included in that file be configurable so that we can when need to, extend it to 48-hours or whatever we need to capture the events necessary for troubleshooting. Then set it back to whatever we wish as our default, which might be 2 hours. I want to acknowledge this idea [Access various logs from Sisense UI under file management option | Sisense Community] as I presume it would also cover the need if the full history of logs within Sisense's own retention policies are made available. But I do, sometimes, also like having a combined file to see events from different logs happing in concurrence without having to reference many different files.
