Unless you're writing software on your own without having to please clients or management (e.g. However, of course the effort doesn't always succeed. Fairly often, my effort succeeds: managers generally want to do right for the business they understand that the tech guy knows things and is worth listening to and sometimes they agree that my proposal is better. I often try to educate, depending on how important I think the issue is. It's not that I think management is stupid it's just that their expertise is in a different area from mine. Sometimes I conclude that I'm dealing with case #2 above. Sometimes I investigate and find out that management really does have good reasons. Management thinks they know what they want, but their request reflects an incomplete understanding as to what technical solutions are possible, and which one would really best serve the business. Management knows what they're talking about: there's some valid business reason why the information needs to be in the requested form and the tech guy just isn't aware of that reason.Ģ. There is a reason why management is asking for it.ġ. This whole article reads like "we in IT are too uninterested in giving management what they want, so I need someone to help me phrase it better". we don't care what you want, this is what we're giving you because we think it's cool. God, it's like IT in the 90s all over again. And your inability/unwillingness to deliver it means that you're either acting thick, or thinking that you are the most important aspect of your business. There is a reason why management is asking for it. If you think a dashboard does the same thing, then maybe your understanding of what they get used for is lacking? They're different things, and you can glean more information from looking at a series of reports, than an instantaneous dashboard. This is stupid, because it sounds like "why would you need your paystub when you can look at your bank balance". a snapshot of your dashboard? Give me a break. You can submit a report to an external entity. "Why would you want reports when you have a dashboard?"īecause a dashboard is a transient thing, which is a snapshot in time and which you can't look back for historical records.Ĭorporations want things they can file and hold onto, and a PDF can do that much better than a dashboard. On the other hand, on the ElasticSearch mailing list when questions were asked about " how do I do reports?" the answer was, and I sum it up here, "Why would you want reports when you have a dashboard?"Īre reports still relevant - the PDF, templated, straight in to your mail kind - or the subset of my clients - we operate mainly in Italy - is a skewed sample of what's the actual reality of access to summary data? Are dashboards - management targeted ones - the current accepted solution or - in your experience - reports are still a hot item for management? None of our clients were easily convinced that a dashboard - Kibana - was a substitute for mail delivered PDFs, even if all the information was there, with custom created panels and selectable date ranges. There was no way for us to create and schedule reports from ElasticSearch - searches for ElasticSearch and Jasper Reports returned nothing apart from people asking how to do it - so we created our own Jasper Reports plugin to create reports from ElasticSearch data, which we released on GitHub a while ago, and we promptly moved along. As we migrated some of our clients to the same stack they kept all asking for the same thing: reporting. Our management wanted to keep the reports they got - and possibly never read - flowing in at the beginning of every week with statistics like sites traffic, servers downtime, security alerts and the works. New submitter MrWHO (68268) writes A while ago we switched for monitoring our systems to the ELK (ElasticSearch, LogStash and Kibana) stack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |