Working with CIs
The list
Configuration items in the sidebar lists the CIs of the units you work in, in the organization picked at the top of the sidebar. The counts at the top filter it in a click: Trouble (degraded, an outage, or at risk through what it relies on), No owner, No relationships (nothing runs on it and it runs on nothing), No support team, Expiring soon (an Expires date, as certificates and domain names have, within 30 days or past), Owned by me and Live. The amber and red ones are the gaps worth closing before an audit. Retired CIs are left out unless you pick that lifecycle.
Filter by class (a class includes the classes below it), lifecycle, health (At risk included), environment, owner, unit, when it was last Updated, or a data property, or search by name, description or any identifier. Columns chooses what the table shows, including data properties.
Add configuration item adds it to the organization picked at the top of the sidebar. It asks for the name, class and units; everything else can wait. Once a class is picked, Properties of the class opens its data properties (those of the classes above it too) to fill in now. Adding, you are its owner when you may be.
A CI's page
| Part | What |
|---|---|
| The header | The class, lifecycle, environment and health, its owner, support team and first identifiers, and Edit. The menu beside it moves the lifecycle on (Make live, Start retiring, Retire, Bring back), and has Ask the owner to review it and Delete. |
| At a glance | Above the tabs: its health and since when; how available it was over 30 days (operational or in maintenance) or since it was added; the open work on it, by kind; how many services rely on it, and how many of them are business services; how much it relies on, and the open incidents there that affect it. Below them, a strip of its health over the same days, and Around it: a small map one step each way, with the work on each box flagged. Open on the map opens the full Dependency map on it. |
| Overview tab | Everything below but the history. |
| About it | Its description. |
| Relationships | What it is joined to, both ways: “Runs on vm-01”, “Runs SHOP-WEB”. Add joins it to another CI of the organization, with a kind that joins two CIs; a service is joined to its CIs from the service's page. One you can't see shows as Hidden (no access). |
| Identifiers and Links | How other tools know it, and its runbooks and dashboards (Links shows only when it has some). |
| Health now | Its health now, what it is at risk through, and its health history (health). |
| Work on it | The open incidents, changes and problems that name it (on records). |
| Details and Properties | The class, lifecycle, environment, owner, support team, units and when it last changed; the data properties of its class. |
| History tab | Changes: every change, with who made it and what changed. The record on a date shows it as it was at a past date and time. |
Map on the Relationships card opens the Dependency map centred on the CI. Whoever may edit the CI adds and removes the relationships from it; one to it is removed from the other end. Every relationship added or removed is in the CI's history, as for services.
Deleting
A CI that something is joined to, or that a case, an incident, a problem or a change names, can't be deleted:
remove its relationships, or retire it instead. Deleting needs
Manage CI classes (ci.settings) and is in the audit log.