io7m | single-page | multi-page | Certusine User Manual
2. Installation
Previous
Front Matter
Up
4. Monitoring
Next

# 3. Configuration

- 3.1. Overview
- 3.2. Durations
- 3.3. Namespace
- 3.4. Options
- 3.5. Accounts
- 3.6. Outputs
- 3.7. DNSConfigurators
- 3.8. Domains
- 3.9. OpenTelemetry
  - 3.9.1. Overview
  - 3.9.2. Traces
  - 3.9.3. Metrics
  - 3.9.4. Logs
  - 3.9.5. Example
- 3.10. Example
- 3.11. Schema

## 3.1. Overview

1
The certusine client accepts an XML configuration file with a very strictly-defined schema. The configuration file is an XML element with the following elements:

### 3.1.2. Properties

- Options
- Accounts
- Outputs
- DNSConfigurators
- Domains
- OpenTelemetry

## 3.2. Durations

1
The certusine package exclusively uses ISO 8601 syntax when specifying durations of time. For example, the string PT1M specifies a one-minute duration. The string PT1H specifies a one-hour duration.

## 3.3. Namespace

1
The xmlns attribute must be present and set to the value "urn:com.io7m.certusine:configuration:2".

## 3.4. Options

1
The Options element specifies global options for the client.
2
The DropUnreferencedCertificates attribute specifies that any certificates that are no longer present in the configuration file should be dropped from the internal certificate store.
3
The DNSWaitTime attribute specifies the amount of time that the client will wait between creating DNS records, and then notifying the ACME servers that the records have been created. This wait time is necessary because DNS records sometimes take time to propagate, and if the client instructs the ACME server to check the records before they have had time to propagate, then the certificate authorization check will fail.
4
The CertificateStore attribute specifies the file that the client will use for its internal database of certificates. Relative paths are resolved relative to the configuration file.
5
The CertificateExpirationThreshold attribute specifies the maximum amount of time before expiration that the client will allow before it attempts to renew a certificate. For example, a value of PT72H means that the client will start attempting to renew a certificate when the certificate becomes due to expire in less than 72 hours.

### 3.4.6. Example Options

    <Options DNSWaitTime="PT5M"
             CertificateStore="store.db"
             CertificateExpirationThreshold="PT72H"/>

## 3.5. Accounts

1
The Accounts element specifies a set of ACME accounts. Most installations will only use a single account.
2
The Name attribute for a given account specifies the name of that account. Names can be anything, but must be unique with respect to other accounts. The names are purely used for organizational purposes internally.
3
The PublicKeyPath attribute for a given account specifies the location of the account's public key. Relative paths are resolved relative to the configuration file.
4
The PrivateKeyPath attribute for a given account specifies the location of the account's private key. Relative paths are resolved relative to the configuration file.
5
The AcmeURI attribute for a given account specifies the base URI that will be used for ACME operations.

### 3.5.6. ACME URIs

URI | Description
--- | ---
https://acme-staging-v02.api.letsencrypt.org/directory | Let's Encrypt staging server
https://acme-v02.api.letsencrypt.org/directory | Let's Encrypt production server

### 3.5.7. Example Accounts

    <Accounts>
      <Account Name="main"
               PublicKeyPath="example.pub"
               PrivateKeyPath="example.pri"
               AcmeURI="https://acme-staging-v02.api.letsencrypt.org/directory"/>
    </Accounts>

## 3.6. Outputs

1
The Outputs element specifies a series of outputs to which issued certificates will be written. Each output has a name, a type, and a set of parameters. Names must be unique with respect to other outputs, and the type must be one of the supported types.

### 3.6.2. Example Outputs

    <Outputs>
      <Output Type="directory"
              Name="main-output">
        <Parameters>
          <Parameter Name="path" Value="/tmp"/>
        </Parameters>
      </Output>
    </Outputs>

## 3.7. DNSConfigurators

1
The DNSConfigurators element specifies a series of external DNS systems in which the certusine client will create records in order to satisfy the DNS challenges posed by the ACME server. Each configurator has a name, a type, and a set of parameters. Names must be unique with respect to other configurators, and the type must be one of the supported types.

### 3.7.2. Example DNSConfigurators

    <DNSConfigurators>
      <DNSConfigurator Type="vultr" Name="vultr-dns">
        <Parameters>
          <Parameter Name="api-key" Value="25DDk6MT+2JI5KBABMysYLPFEOge+MZE3/GiBgrR+CU="/>
          <Parameter Name="domain" Value="example.com"/>
        </Parameters>
      </DNSConfigurator>
    </DNSConfigurators>

## 3.8. Domains

1
The Domains element specifies the certificates within domains that the certusine client will attempt to issue and/or renew. A domain has exactly one account, a set of certificate outputs, and exactly one dns configurator. A domain can have any number of certificates.
2
The Name attribute for a given certificate specifies the name of that certificate. Names can be anything, but must be unique with respect to other certificates. The names are used for organizational purposes internally, and may be used as file names in outputs.
3
The PublicKeyPath attribute for a given certificate specifies the location of the certificate's public key. Relative paths are resolved relative to the configuration file.
4
The PrivateKeyPath attribute for a given certificate specifies the location of the certificate's private key. Relative paths are resolved relative to the configuration file.
5
The Hosts element for a given certificate specifies the hosts within the domain to which the certificate applies. Note that these are not fully-qualified names. Hosts may include wildcards, so for example a certificate may declare a host such as *. To issue a certificate without an explicit hostname (so, for example, to issue a certificate for example.com), simply specify an empty hostname.
6
The OutputReferences element for a domain specifies the names of the outputs to which certificates will be written. It is an error to specify the name of an undeclared output.
7
The DNSConfigurator element for a domain specifies the name of the DNS configurator that will be used to complete DNS challenges by the ACME server. It is an error to specify the name of an undeclared DNS configurator.

### 3.8.8. Example Domains

    <Domain Name="example.com"
            Account="main"
            DNSConfigurator="vultr-dns">
      <Certificates>
        <Certificate Name="www"
                     PublicKeyPath="fake.pub"
                     PrivateKeyPath="fake.pri">
          <Hosts>
            <Host Name="www0"/>
            <Host Name="www1"/>
            <Host Name="www2"/>
          </Hosts>
        </Certificate>
        <Certificate Name="mail"
                     PublicKeyPath="fake.pub"
                     PrivateKeyPath="fake.pri">
          <Hosts>
            <Host Name="mail0"/>
            <Host Name="mail1"/>
          </Hosts>
        </Certificate>
        <Certificate Name="wildcard"
                     PublicKeyPath="fake.pub"
                     PrivateKeyPath="fake.pri">
          <Hosts>
            <Host Name="*"/>
          </Hosts>
        </Certificate>
      </Certificates>
      <OutputReferences>
        <OutputReference Name="main-output"/>
      </OutputReferences>
    </Domain>

## 3.9. OpenTelemetry

## 3.9.1. Overview

1
Note: OpenTelemetry is deprecated as of version 4.0.0. The next major release of the certusine package will expose a Prometheus-compatible metrics endpoint.
2
The OpenTelemetry section of the configuration file configures Open Telemetry. This section is optional and telemetry is disabled if the section is not present.
3
The logical service name should be provided in the LogicalServiceName attribute.

### 3.9.1.4. Telemetry

## 3.9.2. Traces

1
If the OpenTelemetry element contains a Traces element, OTLP traces will be sent to a specified endpoint. The Endpoint attribute specifies the endpoint, and the Protocol attribute can either be GRPC or HTTP.

## 3.9.3. Metrics

1
If the OpenTelemetry element contains a Metrics element, OTLP metrics will be sent to a specified endpoint. The Endpoint attribute specifies the endpoint, and the Protocol attribute can either be GRPC or HTTP.

## 3.9.4. Logs

1
If the OpenTelemetry element contains a Logs element, OTLP logs will be sent to a specified endpoint. The Endpoint attribute specifies the endpoint, and the Protocol attribute must be HTTP.

## 3.9.5. Example

1
An example Open Telemetry configuration:

### 3.9.5.2. Example

    <OpenTelemetry LogicalServiceName="certusine">
      <Logs Endpoint="http://logs.example.com:4317"
            Protocol="HTTP"/>
      <Metrics Endpoint="http://metrics.example.com:4317"
               Protocol="HTTP"/>
      <Traces Endpoint="http://traces.example.com:4317"
              Protocol="HTTP"/>
    </OpenTelemetry>

## 3.10. Example

1
A full configuration file example is as follows:

### 3.10.2. Example

    <?xml version="1.0" encoding="UTF-8" ?>

    <Configuration xmlns="urn:com.io7m.certusine:configuration:1">

      <Options CertificateStore="store.db"
               DNSWaitTime="PT5M"
               CertificateExpirationThreshold="PT72H"/>

      <Accounts>
        <Account Name="main"
                 PublicKeyPath="fake.pub"
                 PrivateKeyPath="fake.pri"
                 AcmeURI="https://acme-staging-v02.api.letsencrypt.org/directory"/>
      </Accounts>

      <Outputs>
        <Output Type="directory"
                Name="main-output">
          <Parameters>
            <Parameter Name="path"
                       Value="/tmp"/>
          </Parameters>
        </Output>
      </Outputs>

      <DNSConfigurators>
        <DNSConfigurator Type="vultr"
                         Name="vultr-dns">
          <Parameters>
            <Parameter Name="api-key"
                       Value="NOTANAPIKEY"/>
            <Parameter Name="domain"
                       Value="example.com"/>
          </Parameters>
        </DNSConfigurator>
      </DNSConfigurators>

      <Domains>
        <Domain Name="example.com"
                Account="main"
                DNSConfigurator="vultr-dns">
          <Certificates>
            <Certificate Name="www"
                         PublicKeyPath="fake.pub"
                         PrivateKeyPath="fake.pri">
              <Hosts>
                <Host Name="www0"/>
                <Host Name="www1"/>
                <Host Name="www2"/>
              </Hosts>
            </Certificate>
            <Certificate Name="mail"
                         PublicKeyPath="fake.pub"
                         PrivateKeyPath="fake.pri">
              <Hosts>
                <Host Name="mail0"/>
                <Host Name="mail1"/>
              </Hosts>
            </Certificate>
            <Certificate Name="wildcard"
                         PublicKeyPath="fake.pub"
                         PrivateKeyPath="fake.pri">
              <Hosts>
                <Host Name="*"/>
              </Hosts>
            </Certificate>
          </Certificates>
          <OutputReferences>
            <OutputReference Name="main-output"/>
          </OutputReferences>
        </Domain>
      </Domains>

    </Configuration>

## 3.11. Schema

1
The XML schema that defines the configuration file format is as follows:

### 3.11.2. Schema

    <?xml version="1.0" encoding="UTF-8" ?>

    <schema xmlns="http://www.w3.org/2001/XMLSchema"
            xmlns:c="urn:com.io7m.certusine:configuration:2"
            targetNamespace="urn:com.io7m.certusine:configuration:2">

      <element name="Options">
        <complexType>
          <attribute name="DNSWaitTime"
                     type="duration"
                     use="optional">
            <annotation>
              <documentation>
                Specifies the amount of time that the client will wait between creating DNS records, and then notifying the
                ACME servers that the records have been created. This wait time is necessary because DNS records sometimes
                take time to propagate, and if the client instructs the ACME server to check the records before they have
                had time to propagate, then the certificate authorization check will fail.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="CertificateStore"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the file that the client will use for its internal database of certificates. Relative paths are
                resolved relative to the configuration file.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="CertificateExpirationThreshold"
                     type="duration"
                     use="optional">
            <annotation>
              <documentation>
                Specifies the maximum amount of time before expiration that the client will allow before it attempts to
                renew a certificate. For example, a value of PT72H means that the client will start attempting to renew a
                certificate when the certificate becomes due to expire in less than 72 hours.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="DropUnreferencedCertificates"
                     type="boolean"
                     default="false"
                     use="optional">
            <annotation>
              <documentation>
                Specifies whether to delete certificates from the database if the
                certificates are not otherwise referenced in the configuration
                file.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="FaultInjection">
        <annotation>
          <documentation>
            Configuration for fault injection. The purpose of fault injection is to make the program fail in various ways at
            runtime in order to verify that metrics and alerting are working correctly.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="FailTasks"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that failing tasks should be injected into the execution of tasks for each domain renewal.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="FailDNSChallenge"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that DNS challenges should be purposefully failed.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="FailSigningCertificates"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that certificate signing should be purposefully failed.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="CrashTasks"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that crashing tasks should be injected into the execution of tasks for each domain renewal.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="CrashDNSChallenge"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that DNS challenges should be purposefully crashed.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="CrashSigningCertificates"
                     use="optional"
                     type="boolean">
            <annotation>
              <documentation>
                Specifies that certificate signing should be purposefully crashed.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Account">
        <complexType>
          <attribute name="Name"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the name of that account. Names can be anything, but must be unique with respect to other
                accounts. The names are purely used for organizational purposes internally.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="PublicKeyPath"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the location of the account's public key. Relative paths are resolved relative to the
                configuration file.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="PrivateKeyPath"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the location of the account's private key. Relative paths are resolved relative to the
                configuration file.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="AcmeURI"
                     type="anyURI"
                     use="required">
            <annotation>
              <documentation>
                Specifies the base URI that will be used for ACME operations.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Accounts">
        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Account"/>
          </sequence>
        </complexType>

        <key name="AccountKey">
          <selector xpath="c:Account"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <element name="Parameter">
        <complexType>
          <attribute name="Name"
                     use="required"
                     type="string"/>
          <attribute name="Value"
                     use="required"
                     type="string"/>
        </complexType>
      </element>

      <element name="Parameters">
        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Parameter"/>
          </sequence>
        </complexType>

        <key name="ParameterKey">
          <selector xpath="c:Parameter"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <element name="Output">
        <annotation>
          <documentation>
            An output destination for signed certificates.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="1"
                    maxOccurs="1">
            <element ref="c:Parameters"/>
          </sequence>
          <attribute name="Type"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                The type of the output. Must be one of the supported output types.
              </documentation>
            </annotation>
          </attribute>
          <attribute name="Name"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                The (unique) name of the output.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Outputs">
        <annotation>
          <documentation>
            A set of output destinations for signed certificates.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Output"/>
          </sequence>
        </complexType>

        <key name="OutputKey">
          <selector xpath="c:Output"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <element name="DNSConfigurator">
        <annotation>
          <documentation>
            A DNS configurator used to create and delete DNS records in response to ACME challenges.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="1"
                    maxOccurs="1">
            <element ref="c:Parameters"/>
          </sequence>
          <attribute name="Type"
                     type="string"
                     use="required"/>
          <attribute name="Name"
                     type="string"
                     use="required"/>
        </complexType>
      </element>

      <element name="DNSConfigurators">
        <annotation>
          <documentation>
            A set of DNS configurators.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:DNSConfigurator"/>
          </sequence>
        </complexType>

        <key name="DNSConfiguratorKey">
          <selector xpath="c:DNSConfigurator"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <element name="Host">
        <annotation>
          <documentation>
            A hostname. Note that this is not a fully-qualified domain name.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="Name"
                     use="required"
                     type="string"/>
        </complexType>
      </element>

      <element name="Hosts">
        <annotation>
          <documentation>
            A set of hostnames.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Host"/>
          </sequence>
        </complexType>

        <unique name="HostsUnique">
          <selector xpath="c:Host"/>
          <field xpath="@Name"/>
        </unique>
      </element>

      <element name="Certificate">
        <annotation>
          <documentation>
            A set of definitions that describe a certificate that will be created and signed.
          </documentation>
        </annotation>

        <complexType>
          <sequence>
            <element ref="c:Hosts"/>
          </sequence>

          <attribute name="Name"
                     use="required"
                     type="string">
            <annotation>
              <documentation>
                The certificate name.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="PublicKeyPath"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the location of the certificate's public key. Relative paths are resolved relative to the
                configuration file.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="PrivateKeyPath"
                     type="string"
                     use="required">
            <annotation>
              <documentation>
                Specifies the location of the certificate's private key. Relative paths are resolved relative to the
                configuration file.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Certificates">
        <annotation>
          <documentation>
            A set of certificate definitions.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Certificate"/>
          </sequence>
        </complexType>

        <key name="CertificateKey">
          <selector xpath="c:Certificate"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <element name="OutputReference">
        <annotation>
          <documentation>
            A reference to an output definition.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="Name"
                     use="required"
                     type="string"/>
        </complexType>
      </element>

      <element name="OutputReferences">
        <annotation>
          <documentation>
            A set of references to output definitions.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="1"
                    maxOccurs="unbounded">
            <element ref="c:OutputReference"/>
          </sequence>
        </complexType>

        <unique name="OutputReferencesUnique">
          <selector xpath="c:OutputReference"/>
          <field xpath="@Name"/>
        </unique>
      </element>

      <element name="Domain">
        <annotation>
          <documentation>
            A set of definitions that define a domain.
          </documentation>
        </annotation>

        <complexType>
          <sequence>
            <element ref="c:Certificates"/>
            <element ref="c:OutputReferences"/>
          </sequence>

          <attribute name="Name"
                     use="required"
                     type="string">
            <annotation>
              <documentation>
                The fully qualified domain name.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="Account"
                     use="required"
                     type="string">
            <annotation>
              <documentation>
                The account to which this domain belongs.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="DNSConfigurator"
                     use="required"
                     type="string">
            <annotation>
              <documentation>
                The DNS configurator that will be used for this domain.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Domains">
        <annotation>
          <documentation>
            A set of domain definitions.
          </documentation>
        </annotation>

        <complexType>
          <sequence minOccurs="0"
                    maxOccurs="unbounded">
            <element ref="c:Domain"/>
          </sequence>
        </complexType>

        <key name="DomainKey">
          <selector xpath="c:Domain"/>
          <field xpath="@Name"/>
        </key>
      </element>

      <simpleType name="OpenTelemetryProtocol">
        <annotation>
          <documentation>
            The protocol used to deliver OpenTelemetry data.
          </documentation>
        </annotation>

        <restriction base="string">
          <enumeration value="HTTP">
            <annotation>
              <documentation>
                The data will be sent using HTTP(s).
              </documentation>
            </annotation>
          </enumeration>
        </restriction>
      </simpleType>

      <element name="Metrics">
        <annotation>
          <documentation>
            Configuration information for OpenTelemetry metrics.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="Endpoint"
                     use="required"
                     type="anyURI">
            <annotation>
              <documentation>
                The endpoint to which OTLP metrics data will be sent.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="Protocol"
                     use="required"
                     type="c:OpenTelemetryProtocol">
            <annotation>
              <documentation>
                The protocol used to send metrics data.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Traces">
        <annotation>
          <documentation>
            Configuration information for OpenTelemetry traces.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="Endpoint"
                     use="required"
                     type="anyURI">
            <annotation>
              <documentation>
                The endpoint to which OTLP trace data will be sent.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="Protocol"
                     use="required"
                     type="c:OpenTelemetryProtocol">
            <annotation>
              <documentation>
                The protocol used to send trace data.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Logs">
        <annotation>
          <documentation>
            Configuration information for OpenTelemetry logs/events.
          </documentation>
        </annotation>

        <complexType>
          <attribute name="Endpoint"
                     use="required"
                     type="anyURI">
            <annotation>
              <documentation>
                The endpoint to which OTLP log data will be sent.
              </documentation>
            </annotation>
          </attribute>

          <attribute name="Protocol"
                     use="required"
                     type="c:OpenTelemetryProtocol">
            <annotation>
              <documentation>
                The protocol used to send log data.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="OpenTelemetry">
        <annotation>
          <documentation>
            Configuration information for OpenTelemetry.
          </documentation>
        </annotation>

        <complexType>
          <sequence>
            <element ref="c:Logs"
                     minOccurs="0"
                     maxOccurs="1"/>
            <element ref="c:Metrics"
                     minOccurs="0"
                     maxOccurs="1"/>
            <element ref="c:Traces"
                     minOccurs="0"
                     maxOccurs="1"/>
          </sequence>

          <attribute name="LogicalServiceName"
                     use="required"
                     type="string">
            <annotation>
              <documentation>
                The logical name of the service as it will appear in OpenTelemetry.
              </documentation>
            </annotation>
          </attribute>
        </complexType>
      </element>

      <element name="Configuration">
        <annotation>
          <documentation>
            The configuration information for the certusine client.
          </documentation>
        </annotation>

        <complexType>
          <sequence>
            <element ref="c:Options"/>
            <element ref="c:Accounts"/>
            <element ref="c:Outputs"/>
            <element ref="c:DNSConfigurators"/>
            <element ref="c:Domains"/>
            <element ref="c:OpenTelemetry"
                     minOccurs="0"
                     maxOccurs="1"/>
            <element ref="c:FaultInjection"
                     minOccurs="0"
                     maxOccurs="1"/>
          </sequence>
        </complexType>

        <keyref name="DomainAccountsExist"
                refer="c:AccountKey">
          <selector xpath="c:Domains/c:Domain"/>
          <field xpath="@Account"/>
        </keyref>

        <keyref name="DomainDNSConfiguratorsExist"
                refer="c:DNSConfiguratorKey">
          <selector xpath="c:Domains/c:Domain"/>
          <field xpath="@DNSConfigurator"/>
        </keyref>

        <keyref name="OutputReferencesExist"
                refer="c:OutputKey">
          <selector xpath="c:Domains/c:Domain/c:OutputReferences/c:OutputReference"/>
          <field xpath="@Name"/>
        </keyref>
      </element>

    </schema>

2. Installation
Previous
Front Matter
Up
4. Monitoring
Next
io7m | single-page | multi-page | Certusine User Manual