I think it would help if the full consequences of having the UI show the wrong status where listed.
Someone trying metron, will, by default , see the wrong thing in the UI for the ONLY sensors they have that are running and doing data. What happens when they try to start them to make them work? One, two or all? What happens when he edits them or try to add transformations? One, two or all? What other things can you do with the sensors in the ui? What happens? Are we recommending aggregation on the list and elsewhere for users? Are we recommending something that is going to ensure they get into this situation? I think this is more than ‘just the wrong thing shown’ in the ui. On April 30, 2019 at 20:48:10, Michael Miklavcic ( michael.miklav...@gmail.com) wrote: The vote for RC1 did not pass and I'd like to kickstart some discussion about what we should do. I started taking a look at PR#1360 and it looks like this isn't quite as close to being able go in as I had originally expected. I want to talk about options here. It seems to me that we can: 1. Wait for PR#1360 to go in, but this is likely going to take more time than originally anticipated 2. Accept the issue in full dev, but add some notes in the developer docs about the current feature gap and why sensors aren't showing status in the management UI when aggregation is enabled. 3. Find some other workable UI solution. 4. Other option? All things considered, I'm personally leaning towards #2 in the short-term, but I think we should probably talk about this a bit before deciding what RC2 should be. Best, Mike
