The Getting started with templates dialog appears automatically when you select + Guardian. To get all the details about a template (for example, which objectives it contains), select Details on the template’s card.
To create a new guardian from a template
In Dynatrace, go to Site Reliability Guardian.
Select + Guardian. The Getting started with templates appears.
Select Use template. The DQL query to retrieve all entities is prefilled. You can edit the DQL query at any time.
Select Run query.
To choose every entity, turn on Select all, or choose the entities you want to guard from the Result list.
Select Apply to template.
Set the name of the guardian at the top.
optional Add a description on the right-hand side.
optional Assign tags.
Refine your objectives on the left-hand side. If you didn't select any guarded entities in step 5, be sure to replace all placeholders (PLACEHOLDER) in your DQL queries with actual values.
Select Create.
To create a guardian without a template, turn on the Create without template option. If you don't want to get the Getting started with templates dialog, then turn off the Show templates when creating a guardian option. You can turn it back on in the upper-right corner in Help.
You can also create a template from an existing guardian.
Go to your guardian.
Select the ellipse next to the title.
Select Templates.
In Use template instead, select Use template.
If you use a template, you'll lose your existing objectives.
Create a guardian manually
You can create a guardian manually, but you need to provide all the required input.
To create a guardian manually
In Dynatrace, go to Site Reliability Guardian.
Select + Guardian.
Select Create without template.
Set the name of the guardian at the top.
optional Add a description on the right-hand side.
optional Assign tags.
Add objectives on the left-hand side. Use a custom DQL query, or reference an existing SLO.
Select Create.
Templates
The following examples are provided:
Template
Description
Four golden signals
Safeguard your service with the four golden signals: latency, traffic, errors, and saturation. This minimum set of objectives focuses on what matters regarding service reliability and performance.
Kubernetes workload saturation
Safeguard your Kubernetes environment with dedicated resource utilization objectives for a Kubernetes workload (i.e., K8s deployment). The objectives focus on memory and CPU consumption of the workload.
Kubernetes cluster saturation
Constantly check the resource consumption of your Kubernetes environment by validating CPU and memory objectives of a Kubernetes cluster.
Kubernetes namespace saturation
Safeguard your Kubernetes environment with dedicated resource utilization objectives for a Kubernetes namespace. The objectives focus on memory and CPU consumption of the namespace including a reliability objective on the container restarts.
Host utilization and saturation
Protect your infrastructure with resource consumption and saturation objectives for a dedicated host.
Security gate
Establish a security gate in your release process to ensure your releases have no known and exploitable vulnerabilities.
Entity selection for an objective
You can select which entities to use for an objective. When selecting an entity, it is prefilled with the correct DQL queries for the objective. The prefilled DQL query helps to configure the objective properly for that particular entity.
Template entity selection enables you
To select the right service/entity to guard.
To define the proper objectives for that particular service/entity.
It is also possible not to select entities. The DQL objectives need to be adjusted afterward, as they will just filter for something similar to HOST-PLACEHOLDER.