In response to: Dormant Data cleanup in TADDM - A Customer StoryWonderful article. Dormant entries that are not addressed by the GUI interface are the bain of TADDM. One thing we do to see gauge what CIs classes might be candidates for checking for dormant records is:
Tivoli Application Dependency Discovery Manager (TADDM) Sensors and Reports Community
This forum is for all questions related to TADDM.
ColetteFinneran 270000Y97G 176 Views
Extending IBM TADDM Discovery and Configuration Change Management to Docker Containers
Author: Manish Lakhani (Aricent - IBM's Development Partner for IBM TADDM))
The consumer of today has changed a lot since the age of the first Industrial Revolution in the 19th century. Today, we are living in the world of Industry 4.0, where integrated computing, networking and physical processes are revolutionizing manufacturing. This has made the consumer more demanding than ever – they want performance driven products, they want variety, they want a fully integrated ecosystem and most importantly, they want everything now - at the speed of a nanosecond!
Digital technology is helping the consumer get what they want, whenever they want, and from wherever they want. It is transforming businesses and industries to serve consumers more effectively and efficiently. Ecommerce has changed the shopping experience, Online learning platforms have changed the education system, Digital diagnostic tools have changed health and wellness industry – the list is endless...
In an environment where speed is critical, technology developers require tools that allow them fast access to resources, minimize process overhead, and enable them to be more productive. This is where Docker comes in to assist developers in efficiently deploying the applications.
WHAT IS DOCKER?
However, managing all the Docker containers and applications can become overwhelming. Adequately protecting and managing a large volume of containers may require another level of resources and capabilities.
IBM TADDM application discovers Docker as a part of an overall cloud while controlling sprawl and infrastructure costs.
Tivoli Application Dependency Discovery Manager (TADDM) is a configuration management tool that helps IT operations personnel ensure, maintain and improve application availability in an enterprise.
TADDM is primarily an application which maps out IT network infrastructure, getting complete information about each and every element (Application Discovery) and finds out the relationships between each (Application Dependency).
For example, using TADDM, we can easily find out that Application A accesses Database E which is running on server F and thus Application A’s dependency on server F.
TADDM’s new release - FP04, provides a suite of software that can detect and discover Docker clusters, hosts, host attributes, containers, and overlay networking stacks from the deployed Docker clusters or individual Docker hosts.
TADDM discovers the following Docker host elements:
TADDM can also detect Docker Swarm and discover following Docker Swarm cluster elements:
For more information about IBM TADDM 7.3 FP04, please go to the IBM Knowledge Center.
jeegan 06000169WU 2,397 Views
TADDM Blog for ALL things TADDM related: https://www-950.ibm.com/blogs/taddm/?lang=en_us
For specific questions / concerns on Sensors & Reports you can use this Blog or the Blog reference above.