rusackas commented on issue #41711: URL: https://github.com/apache/superset/issues/41711#issuecomment-4884184409
You're more than welcome to open a new SIP (I'll convert this to a Discussion rather than an Issue in the meantime). I think that'll be cleaner than reopening the old one, especially if you want to own putting it through the SIP process. That said, I think you'll likely run into similar problems mentione on the other SIP... namely: 1) The scope of what people do and don't want in the dashboard will be largely subjective... people might not want to surface things that include PII 2) Some people will want more/fewer/different things monitored. I'm not sure if there's a "one size fits all" solution here Database agnosticism and opt-in deployment do sound like important facets though. There are any other number of things that come through the logging service that people may or may not want in their monitoring/activity dashboards. I guess this all points to the question of if/how it can be configurable/customizable. I have nothing against any of this, just don't know how to make it perfect/universal. I look forward to the SIP if you want to go down that road :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
