Exposing the data backbone
# general
d
I actually believe (this may be controversial) that exposing the data backbone in a more accessible way would benefit UMH. I feel the end-to-end data pipeline is somewhat lacking. Ingress is really strong with Benthos, but outgress is missing in terms of ease of access. The Grafana plugin from before was very handy and useful for those in the company without SQL knowledge (which is over 95% of the people). It allowed users to simply browse assets, select a tag, and visualize the data. The digital transformation managers always say you can gather all the data you want, but you need to put it into action. The people with the best ideas for how to use the data don’t necessarily know how to handle databases. I believe there needs to be a more simplified way of working with the data. Thoughts on this are welcome. This is something I’ve noticed in the industry, and @Jermuk had a different opinion when we last spoke. (not trying to doubt the strategy of UMH; I absolutely love you guys, Just here to learn new things and have an open discussion)
j
This sounds reasonable! Does anyone have any better idea on how we can expose the data to a normal user, but also satisfy the needs of a power user? The idea could be to have some kind of SQL query builder, which you can execute within the Management Console. If you don’t care about SQL, you could simply just use the nice UI/filters, and check the results. If you do care, you could build on them
d
The old datasource was a really good addition and one of the better features with umh, it makes the visualization of data super easy.. My boss(with little to none knowledge of sql etc) setup several dashboards in grafana quite quick using the umh datasource.. I strongly believe that this should be improved and used as the main datasource.
what i also would like to see in a datasource is buffering so we could stream data in a better way. Say for example we have a dashboard looking at the last 12h and we update every 5s, instead of query the db for 12h you should query for the last 5s and update the buffer. This would put less stress on the db. This would however require the datasoure to keep track on the dashboards in grafana to know what to have in the buffer. it would also require a tool like redis to keep the data in the ram.
d
yes but i think thats a mistake from our side @DanielH, i'm facing the same issue atm. i query the database for realtime data but actually that's not required. it would be better to connect your grafana to the kafka broker and stream data from there
it has a dataretention set so it acts as a database as well
j
Here are our thoughts: Summary - Accessibility for Non-Technical Users: Users like @Diederik and @DanielH expressed that the current data pipeline lacks ease of access for users without SQL knowledge. They found the previous Grafana plugin useful for visualizing data without needing to write SQL queries. - Simplified Data Interaction: There is a need for a more straightforward way for OT personnel to interact with data, including selecting assets, tags, and visualizing data without deep technical expertise. What we think of it: - It is quite a lot of effort to make the Grafana Plugin. Also, the Grafana Plugin would not work for power users anymore, which does not fit ointo our product vision (https://learn.umh.app/blog/why-most-manufacturing-software-sucks-and-what-we-do-differently-at-umh/) - Instead, we make the Tag Browser easier to be used by an OT person. So we want to make it easier to generate SQL queries, and get their results. Therefore, a power user and a entry-level suers can both work on the same system with the same code. We can do it step by step: - Implement an interval selector within the Tag Browser to allow users to modify the time range of data queries easily. - Add options for calculating averages, minimums, maximums, etc., directly within the Tag Browser. - Hide the SQL query behind a collapsible element to reduce complexity for non-technical users while still providing access for power users. - “Open in Grafana” Button: Include a button that allows users to open the generated query directly in Grafana, facilitating easy dashboard creation and data visualization. - Filter Enhancements: Introduce more filters to help generate SQL queries without manual input, making it easier for OT personnel to retrieve the data they need.
Additionally, we should improve teh Tag Browser itself: - Modify the Tag Browser to show all tags, including historical ones, not just those from the last restart. - Allow users to fetch the last ‘n’ values of a tag directly from Kafka if available, providing quick access to recent data.
What are your thoughts on this proposal?
d
proposed ideas sound good to me only “Open in Grafana” Button: Include a button that allows users to open the generated query directly in Grafana, facilitating easy dashboard creation and data visualization. seems a bit much to me, sounds like a lot of effort for just a small added value
j
should be quite easy to do, see also how our hosting vendor fly.io does it
seems to me like a good balance between easyness, and power user
How important would you say would be the capability to execute the query inside of the tag browser? would it be a little bit confusing to have data from kafka, and from the database shown in the same UI?
d
i dont need to be able to execute them in the console, copying them to grafana and working there is fine for me :p
j
also the normal OT person?
thinking about them as well
we want to give the average guy on the shopfloor access to the management console as well (maybe just for the tag browser)
d
in my opinion they should not havea access to the management console
they will be confused building it in one tool, then having it in a second tool
would be better to have the grafana plugin functionallity again for them
(Factry.io has this and people love it)
i saw it myself at A&S energies, one of their costumers 2 operators discussing "hey, wouldnt it be nice to see this value live while we're adjusting the burner?" they logged into the historian, found the tag, added it in an empty dashboard and made the adjustment while looking at the screen
the best & most tanglible proof of value of digitilization i ever saw at a costumer
this is what we need to be able to make happen
if it's not in their hands, the opportunity gets lost in translation to "the data team"
that's why i'm so keen on having it end to end
without that we dont provide a real solution for the end costumer, we just have tools to make it doable for ourself (the engineers)
d
yes, i would still claim that the umh-datasource is really easy to use for the shopfloor manager.. as i wrote before, my boss have created several dashboards using the datasource and he does not understand sql.. I build all my dashboards using SQL since it gives me more freedom to aggregate data but for simple data visualisation the datasource is a really nice addition.
j
what would be missing in the management console so that OT people can also use the tag browser and work with the data?
we were thinking about things like: - open in grafana (which then gets rendered inside of the management console, centralized authentication through the management console as well so you are logged in with the same user as you are in the management console) - fallback VPN, so that you can access Grafana indendent on whether you are in the same network or not
it makes sense that someone works as close as possible to the data, e.g., for alerts
d
if you do something like this, first use rights has to be implemented user A has admin right (create instance, view kube errors,...), user B can only see namespace browser and querries
Cant trust anyone using my instance :p too afraid they will break my system hahah
Fallback vpn is nice tho
i currently have a workaround to have that functionality
grafana cloud with Private data source connect (PDC)
2 Views