NEW

BLOG

The IT challenge
Allprobe Technical Writer
2018-12-16 11:10:47

 

Master your IT with simplicity and clear vision


IT is everywhere these days; almost everything is backed up with IT. By saying IT, I mean systems supported by servers, Cloud providers, Services, Microservices, APIs, Data Centers, Networking providers and so on, beside The dense backbones companies & organizations have to deals today with more and more considered to be IT assets.





Managing all of those assets the right way is not always straightforward or being thought.
We can argue on many issues within this topic, and we can divide it to many little topics, then we try to see how we came up, we make mistakes, we learn, we correct, we try to do better every day.


While every business, network, IT department, IT topology is different, it is hard to come up with a master tool to be great for every use case.
I'm in what we can say modern IT for almost 20 years, over the years I had to deal and came across many internet topologies supported by machines. Mostly Linux servers on all shapes and sizes. I tested & worked with many tools to maintain everything; I mainly worked with open sourced products such as Zabbix, Nagios, and some more advanced tools such as The excellent Micro Tick The dude monitoring system. Those are very sophisticated tools, but something was always missing. Over the years, mainly last few years, there was a jump in understanding how IT should be handled, indexed, monitored, and so on. Big data and AI came into place as well and broadened the possibilities.
Microservices also become a big topic for designing applications and systems and require a special kind of approach.


How do we manage it all? What are the main topics and challenges? First, we need to acknowledge that IT involves many layers of responsibilities and subjects. In this blog, I will be focusing and talk about one of the most critical parts of IT and the foundations: IT infrastructures(on-prem and cloud), the monitoring and the IT management layers.


From my perspective, IT management & monitoring should be under the same roof. Monitoring is tightly integrated into IT as well as IT assets management. They share the same sets of common objects and mostly handled by the same departments or people. The management layer should also be used by none IT stuff such as managers; it will give management a good understanding of what's going on and a good view of things belonging and being used.


ITIL to the rescue





ITIL (Information Technology Infrastructure Library) - Responding to growing dependence on IT. The standard is a set of detailed practices for IT service management (ITSM / ITAM) that focuses on aligning IT services with the needs of the business.
ITIL is very vast and going down to tiny details in every possible IT use case and businesses management.

ITIL - cons & pros
While dealing & detailing all IT situations & management paths, not all aspect of the standard is needed by most use cases, for most cases, the complexity level is overwhelming and counterproductive.


Layers





A productive ITIL management tool should be divided into layers while allowing all layers to communicate & be integrated to some extent with each other.
It's not entirely clear what are the integration levels of each layer of the IT management module; My opinion is that the management system should distinguish between IT(with management personnel) and none IT personnel, by saying personnel I mean, employee, service provider, freelancers & outsourcing.
Another good option is not to distinguish between IT and none IT but instead focus on ACLs and access levels(permissions), however, I think that tasks like support ticket systems should be other than the pure IT tasks and at most allow the integration between the two with API options.

There are many examples where a distributed approach is best feet like Microservices, some programming(monolithic) practices, modern distributed systems like NoSQL, and so on. But even with a distributed approach, we need some central point of view, something that makes sense of everything but yet not complicating things too much.


Here comes CMDB




A configuration management database (CMDB) is a database that contains all the relevant IT items(CIs) and then desirable present the data in a most meaningful way through Visual CMDB. Not only CMDB holds all the items; it also contains all the relations between all the items conforming a big multidimensional relations map.


Some of the main functions of CMDB are:

- Service catalog
- Problem management
- Incident management
- Impact analysis
- Service level management
- Retroactive root cause analysis
- Full Lifecycle Management of Configuration Items


Each of those essential topics has another meaningful set of options.
A good example is cataloging all the software & hardware Items with a useful & meaningful set of values unique for the CMDB Type (brunch) "Licenses" like a warranty expiration date. An application management layer for CMDB data should make good use of those values by creating valuable reports and alerts specifically for licenses and warranties management.


SLA measurement high importance
CMDB made easy
The IT challenge
The IT challenge
Allprobe Technical Writer
2018-12-16 11:10:47

 

Master your IT with simplicity and clear vision


IT is everywhere these days; almost everything is backed up with IT. By saying IT, I mean systems supported by servers, Cloud providers, Services, Microservices, APIs, Data Centers, Networking providers and so on, beside The dense backbones companies & organizations have to deals today with more and more considered to be IT assets.





Managing all of those assets the right way is not always straightforward or being thought.
We can argue on many issues within this topic, and we can divide it to many little topics, then we try to see how we came up, we make mistakes, we learn, we correct, we try to do better every day.


While every business, network, IT department, IT topology is different, it is hard to come up with a master tool to be great for every use case.
I'm in what we can say modern IT for almost 20 years, over the years I had to deal and came across many internet topologies supported by machines. Mostly Linux servers on all shapes and sizes. I tested & worked with many tools to maintain everything; I mainly worked with open sourced products such as Zabbix, Nagios, and some more advanced tools such as The excellent Micro Tick The dude monitoring system. Those are very sophisticated tools, but something was always missing. Over the years, mainly last few years, there was a jump in understanding how IT should be handled, indexed, monitored, and so on. Big data and AI came into place as well and broadened the possibilities.
Microservices also become a big topic for designing applications and systems and require a special kind of approach.


How do we manage it all? What are the main topics and challenges? First, we need to acknowledge that IT involves many layers of responsibilities and subjects. In this blog, I will be focusing and talk about one of the most critical parts of IT and the foundations: IT infrastructures(on-prem and cloud), the monitoring and the IT management layers.


From my perspective, IT management & monitoring should be under the same roof. Monitoring is tightly integrated into IT as well as IT assets management. They share the same sets of common objects and mostly handled by the same departments or people. The management layer should also be used by none IT stuff such as managers; it will give management a good understanding of what's going on and a good view of things belonging and being used.


ITIL to the rescue





ITIL (Information Technology Infrastructure Library) - Responding to growing dependence on IT. The standard is a set of detailed practices for IT service management (ITSM / ITAM) that focuses on aligning IT services with the needs of the business.
ITIL is very vast and going down to tiny details in every possible IT use case and businesses management.

ITIL - cons & pros
While dealing & detailing all IT situations & management paths, not all aspect of the standard is needed by most use cases, for most cases, the complexity level is overwhelming and counterproductive.


Layers





A productive ITIL management tool should be divided into layers while allowing all layers to communicate & be integrated to some extent with each other.
It's not entirely clear what are the integration levels of each layer of the IT management module; My opinion is that the management system should distinguish between IT(with management personnel) and none IT personnel, by saying personnel I mean, employee, service provider, freelancers & outsourcing.
Another good option is not to distinguish between IT and none IT but instead focus on ACLs and access levels(permissions), however, I think that tasks like support ticket systems should be other than the pure IT tasks and at most allow the integration between the two with API options.

There are many examples where a distributed approach is best feet like Microservices, some programming(monolithic) practices, modern distributed systems like NoSQL, and so on. But even with a distributed approach, we need some central point of view, something that makes sense of everything but yet not complicating things too much.


Here comes CMDB




A configuration management database (CMDB) is a database that contains all the relevant IT items(CIs) and then desirable present the data in a most meaningful way through Visual CMDB. Not only CMDB holds all the items; it also contains all the relations between all the items conforming a big multidimensional relations map.


Some of the main functions of CMDB are:

- Service catalog
- Problem management
- Incident management
- Impact analysis
- Service level management
- Retroactive root cause analysis
- Full Lifecycle Management of Configuration Items


Each of those essential topics has another meaningful set of options.
A good example is cataloging all the software & hardware Items with a useful & meaningful set of values unique for the CMDB Type (brunch) "Licenses" like a warranty expiration date. An application management layer for CMDB data should make good use of those values by creating valuable reports and alerts specifically for licenses and warranties management.


SLA measurement high importance
CMDB made easy
The IT challenge