Services are the components that you want to display and report on with a status dashboard - they can be websites, APIs, servers, or anything else about which your users and customers require timely status information. One of the first things you'll want to do when setting up your StatusDashboard account is add some services. Services are global within your account, and once created, may be imported into one or more of your status dashboards or digital signs. Once you add services, they'll immediately be available for adding to any of the status dashboards or digital signs within your account.
Global services can be created and managed by navigating to Services.
Service Attributes
Services have the following attributes, some of which may be overridden once the service is added to a status dashboard:
Attribute |
Description |
Override Option |
Name |
The service name is how the service will be represented anywhere that services are shown (e.g. the status dashboard, digital sign, email notifications, etc). Service names must be unique within your StatusDashboard account. |
No |
Description |
When a service description is entered, an information indicator will appear next to the service name in the dashboard display, which when hovered over, will display the associated information text. |
Yes |
Group |
Service groups allow you to visually group the services on a status dashboard. For example, if your organization has infrastructure and users on multiple continents around the world, you may wish to group your services by geography (e.g. North America, South America, Africa). By default, when a service is created, it is assigned the service group "default". |
Yes |
Hidden (Dashboard) |
When services are hidden, they will not appear anywhere on the status dashboard. Additionally, hidden services will not be displayed in the notifications subscription pages of the status dashboard when selecting individual services. |
Yes |
Hidden (User Notifications) |
When services are hidden from user notifications, they will not appear in any notifications sent from StatusDashboard (e.g. email, SMS, webhooks). |
Yes |
PagerDuty |
When the PagerDuty integration is being utilized, PagerDuty service id mapping must be entered here. Any services that will be part of PagerDuty created events must have the PagerDuty service id entered here. Custom descriptions can also be entered here, which will over-ride the description sent by PagerDuty for any events. |
No |
Webhook (inbound) |
When the inbound webhook integration is being utilized, third party application service id mapping can optionally be entered here (this is not required if you want to use StatusDashboard service ids with inbound webhooks). Any services that will be part of inbound webhooks that utilize third party service ids must have a valid id entered here. |
No |