Vision for costs in data dashboards (and alerts) #2432
kishore-jalleda
started this conversation in
General
Replies: 1 comment 1 reply
-
Yes, I believe that's the idea -- being able to measure the cost of maintaining data sources that can be used for 1) generating alerts/ events that need to be investigated/ analyzed 2) investigating issues during the handling of incidents or cases. The vision for alerts is that Dispatch will monitor the health of the data sources you have onboarded and it will alert you when those are not available (e.g. by performing a SQL query against a table). Sources, queries, and alerts need more work. @kevgliss will resume his work on them when he's back. He can also provide more information about the vision for them. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am trying to wrap my head around the costs reported with data dashboards and hoping to get the vision. Specifically, I am trying to understand what the below metrics mean. Instinctively, I am like, incidents have cost associated w/them, but what about the data sources -> costs mapping? Then, when I looked at the code, I see the
cost
attr in the Source class, and it probably means the cost of maintaining that source. I still feel that I am probably missing something. Anyway, here's what I think:incidents
attr) desc limit 5?)Also, I see model classes defined for alerts, along with methods, api's, etc, and the rel with class source, but don't see a whole lot of it elsewhere in the code Am I missing anything? what's the vision for alerts?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions