[comment]: # ({6192d6e3-6192d6e3})
# 1 Services
[comment]: # ({/6192d6e3-6192d6e3})
[comment]: # ({0f670bd5-dfc7b2ba})
### Overview
In this section you can see a high-level status of whole services that have been
configured in Zabbix, based on your infrastructure.
A service may be a hierarchy consisting of several levels of other services,
called "child" services, which are attributes to the overall status of the
service (see also an overview of the [service monitoring](/manual/it_services) functionality.)
The main categories of service status are *OK* or *Problem*, where the *Problem* status
is expressed by the corresponding problem severity name and color.
While the view mode allows to monitor services with their status and other details, you can
also [configure](/manual/web_interface/frontend_sections/services/service#editing-services) the service hierarchy in this section (add/edit services, child services)
by switching to the edit mode.
To switch from the view to the edit mode (and back) click on the respective button
in the upper right corner:
-  -
view services
-  -
add/edit services, and child services
Note that access to editing depends on [user role](/manual/web_interface/frontend_sections/users/user_roles)
settings.
[comment]: # ({/0f670bd5-dfc7b2ba})
[comment]: # ({a3df40db-9c989a32})
### Viewing services
{width="600"}
A list of the existing services is displayed.
Displayed data:
|Parameter|Description|
|--|--------|
|*Name*|Service name.
The service name is a link to [service details](#service-details).
The number after the name indicates how many [child services](#service-details) the service has.|
|*Status*|Service status:
**OK** - no problems
**\** - indicates a problem and its severity. In case of multiple problems, the color and severity of the most critical problem are displayed.|
|*Root cause*|Underlying problems that directly or indirectly affect the service status are listed.
The same problems are listed as returned by the {SERVICE.ROOTCAUSE} [macro](/manual/appendix/macros/supported_by_location).
Click on the problem name to see more details about it in *Monitoring* → *Problems*.
Problems that do not affect the service status are not in the list.|
|*Created at*|The time when the service was created is displayed.|
|*Tags*|[Tags](/manual/it_services/service_tree#service-tags) of the service are displayed. Tags are used to identify a service in service [actions](/manual/web_interface/frontend_sections/alerts/actions) and [SLAs](/manual/web_interface/frontend_sections/services/sla).|
[comment]: # ({/a3df40db-9c989a32})
[comment]: # ({84099469-84099469})
##### Buttons
View mode buttons being common for all sections are described on the
[Monitoring](/manual/web_interface/frontend_sections/monitoring#view_mode_buttons)
page.
[comment]: # ({/84099469-84099469})
[comment]: # ({6363368e-a1995254})
##### Using filter
You can use the filter to display only the services you are interested in.
{width="600"}
|Parameter|Description|
|--|--------|
|*Name*|Filter by service name.|
|*Status*|Filter by service status.|
|*Only services without children*|Mark the checkbox to display only services without child services. This parameter is available only in services [edit mode](#editing-services).|
|*Only services without problem tags*|Mark the checkbox to display only services without problem tags. This parameter is available only in services [edit mode](#editing-services).|
|*Tags*|Filter by service tag name and value, or service problem tag name and value (in services [edit mode](#editing-services)).
It is possible to include as well as exclude specific tags and tag values. Several conditions can be set. Tag name matching is always case-sensitive.
There are several operators available for each condition:
**Exists** - include the specified tag names;
**Equals** - include the specified tag names and values (case-sensitive);
**Contains** - include the specified tag names where the tag values contain the entered string (substring match, case-insensitive);
**Does not exist** - exclude the specified tag names;
**Does not equal** - exclude the specified tag names and values (case-sensitive);
**Does not contain** - exclude the specified tag names where the tag values contain the entered string (substring match, case-insensitive).
There are two calculation types for conditions:
**And/Or** - all conditions must be met, conditions having the same tag name will be grouped by the Or condition;
**Or** - enough if one condition is met.|
[comment]: # ({/6363368e-a1995254})
[comment]: # ({f6008afa-512ba2ca})
### Editing services
Click on the *Edit* button to access the edit mode. When in edit mode, the listing
is complemented with checkboxes before the entries and also these additional options:
-  -
add a child service to this service
-  -
edit this service
-  -
delete this service
{width="600"}
To [configure](/manual/it_services/service_tree#service-configuration) a new service, click on the
*Create service* button in the top right-hand corner.
[comment]: # ({/f6008afa-512ba2ca})
[comment]: # ({14689056-10028f4d})
### Service details
To access service details, click on the service name. To return to the
list of all services, click on *All services*.
Service details include the info box and the list of child services.
{width="600"}
To access the info box, click on the *Info* tab. The info box contains the
following entries:
- Names of parent services (if any)
- Current status of this service
- Current SLA(s) of this service, in the format `SLA name:service level indicator`. 'SLA name' is also a link to the SLA report for this service. If you position the mouse on the info box next to the service-level indicator (SLI), a pop-up info list is displayed with SLI details. The service-level indicator displays the current service level, in percentage.
- Service tags
The info box also contains a link to the [service configuration](/manual/it_services/service_tree#service-configuration).
To use the filter for child services, click on the *Filter* tab.
When in
edit mode, the child service listing is complemented with additional
editing options:
-  -
add a child service to this service
-  -
edit this service
-  -
delete this service
[comment]: # ({/14689056-10028f4d})