To create a service:
To create a service within a View, you must have the appropriate permission to access the View.
- On the Services dashboard, click Create Service in the top right of the Service List dashlet or via the Service List dashlet's Overflow Menu. You can also access this form by selecting an object in a View dashboard and right clicking to open its context menu, then clicking Create Service.
- The Create Service form will slide in on the right.
- Enter a name for the service in the Name field.
- If you running a multi-server install, specify which managing server you want the service to be under in the Managing Server dropdown field. If you are running a single server install, this field will be hidden.
- Add objects, components and network paths to your service in the Service Components field. Either drag the objects in from another tab or browser, or click + Add a new component to open an Explorer, in which you can navigate to an select your desired managed object or component. Click Done to add the component to the service, otherwise click Cancel.
- The components within the service will then be listed beneath the Service Components field. To delete components that you have selected, click on the component in this list, which will then provide you with the Remove component from this service field. Click this and then click Done to confirm the removal, otherwise click Cancel.
- Select which logical operator you want to apply to the components in the service in the Service Logic Type field. Choose from one of the following (the default is And):
- None - service does not return a status. This is the equivalent of turning off the service. This can be used when you do not want the state of a sub-service to contribute to the state of its parent service.
- And - service requires all of its components or sub-services to be up.
- Or - service requires any of its components to be up.
- Not - service requires that one component is not up, e.g. a backup link should be down, and if it is up then there is a problem in service delivery.
- At Least - service requires two criteria, see below for the Least Number of Components and Degraded Threshold fields.
- If Component Composition is set to At Least, the Least Number of Components field will become available. In this field, enter the least number of components that need to be up for the service to be fully operational.
- If Component Composition is set to At Least, the Degraded Threshold field will be available. In this field, enter the number of components that specify the degraded threshold - a service with as few as this many components in an up state but less than the At Least value will deliver a degraded state.
- Specify if you want events to be raised when the service state changes in the Raise State Change Events field. By default, this is switched to On.
- Click the Advanced Settings field to open the Advanced form.
- Enter a description of the service in the Service Description field.
- Specify if you want the service to be tagged as Standard, for a Branch perspective or for a CIO perspective in the Service Tags field. This relates to producing reports on the service - if you select Branch, this service will be available for the Branch Office Perspective reports, and if you select CIO, this service will be available for the CIO Perspective reports. By default, Standard is chosen. Note, Service Tags do not impact the running of the service - they only influence which reports you can select for it. Please see the articles on managing branch offices and setting up CIO perspectives for further help and information on these topics.
- Specify if you want to aggregate traffic across all ports in the Aggregate Traffic Across All Ports field.
- Specify if you want a service with an unknown state to be treated as down in the Treat Unknown State as Down field.
- Enter the target SLA performance for the service, measured in %, in the SLA Availability Goal field.
- Click Done in the top right of the form to save your settings, otherwise click Cancel.
- Click Save in the top right of the form to save your service, otherwise click Cancel.
To create a sub-service:
You can create service hierarchies by creating a sub-service. A sub-service is contained within a parent service.
Building a service hierarchy means that you can use the state of a sub-service to help determine the state of a parent service.
- Navigate to the Summary dashboard of the service within which you want to create a sub-service.
- Click Create Sub-Service in the top right of the dashboard, or via the Service Components dashlet's Overflow Menu. This will open the Create Sub-Service form on the right of the browser.
- At the top of the form is the Parent Service field, which specifies the selected service that will be the parent to this sub-service.
- Below the Parent Service field, the rest of this form requires a user to complete the same forms as when creating a service (as described above).
- Click Done in the top right of the form to save and create the sub-service, otherwise click Cancel.
To edit a service:
- In the Services dashboard, go to the Service List dashlet (which is a Service Summary dashlet) and select the service that you want to edit.
- Click the Overflow Menu, or right click the selected service to open its Context Menu, and then click Edit Service.
- This will open the Edit Service form on the right of the browser. This form has the same fields as the Create Service form as detailed above.
- Click Save in the top right of the form to save your changes, otherwise click Cancel.