We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Connecting the Dots with PowerShell

Formal Metadata

Title
Connecting the Dots with PowerShell
Title of Series
Number of Parts
60
Author
License
CC Attribution - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language
Producer
Production Year2018

Content Metadata

Subject Area
Genre
Abstract
One of PowerShell's greatest strengths is its ability to glue pretty much any technologies together. We'll use that strength to pull data from a number of services, connecting the resulting dots with a graph database that could be used as a lightweight CMDB. We'll talk about: * Different interfaces PowerShell can use, from modules to .NET libraries * Graph databases like Neo4j, and how these can be useful for sysadmins * A practical (janky) CMDB, and why these can be useful ## Why the topic: I'm a fan of CMDBs that have useful data. They can drive automation, monitoring and alerting, reporting, and anything else that benefits from visibility. It just so happens that: * This is a great way to illustrate the various ways to talk to things in PowerShell (modules, web APIs, .NET libraries, binaries, etc.) * Graph databases are awesome, and map to real life systems more easily than the cumbersome fun of primary keys, foreign keys, and strict schemas * Neo4j has a free, cross platform community edition, and there's a simple PowerShell module to work with it * We can instill other important lessons, e.g. modules/abstraction, community/sharing * We can provide a practical example that folks without a reasonable CMDB could borrow and extend * Heavy weight, expensive, actual CMDBs are a poor fit for shops adopting DevOps practices and principles