Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

why not API as a CI (configuration item) ?


I have never seen APIs in CI lists.

why ??

2 answers

0 votes

I would agree that the 'API' itself would not be in a CMDB as a CI.

However, I would consider 2 related points:

a) API-End-Points may very well be CIs.

b) APIs may exist as 'Products' since APIs have a lifecycle as well

Well, I've already explained why an API (and hence its endpoints) isn't a CI itself before.   They don't meet the definitions.

API as a product though - I'd qualify that as "a component of a product", but yes, they should be considered as products.  I mean, an API on its own is not a product because it's utterly useless without the thing it is an interface to, but it's certainly a distinct part of a product.  (Just thinking of Jira, you've got Jira, the java API, the REST API, and then all the other bits - Java and REST APIs for Software, Service Management, Insight, Advanced roadmaps and so on)

0 votes

Because APIs are not configuration items.

why aren't they considered as CI ?

What do think a configuration item is?

I got this definition from IBM, and I think APIs has the characteristics :

A configuration item (CI) is any service component, infrastructure element, or other item that needs to be managed in order to ensure the successful delivery of services.

Each CI has several characteristics:

  • A classification, or type, which indicates what kind of item it is.
  • Attributes, which vary by classification and describe the characteristics of the individual CI.
  • A status value, which represents the CI's state in the lifecycle used for CIs of this classification.
  • Relationships, which indicate how the CI is related to other CIs.
  • An owner, the person who is responsible for the CI.

CIs vary in complexity, size, and type. They can range from an entire service, which may consist of hardware, software, and documentation, to a single program module or a minor hardware component. The lowest-level CI is usually the smallest unit that will be changed independently of other components.

And there you go - the API does not have a variation of classification, a status, relationships with other things or an owner (beyond it belonging to the system you are in).  They are not even configured in any way.

I am not sure you really mean "API" now.

all right, thanks !

Like Nic Brough _Adaptavist_ likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

735 views 5 13
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you