Pulse Settings

Please see Component Settings for details on how to configure Pulse's logging levels, network settings, and authorization parameters. Only non-standard setting component is the Authorization Issuer that will be discussed below.

{
  "DetailedErrors": true,

  "Serilog": {
    "MinimumLevel": {
      "Default": "Warning",
      "Override": {
        "Timebase.Pulse": "Information"
      }
    }
  },

  "Kestrel": {
    "Endpoints": {
      "Http": {
        "Url": "http://0.0.0.0:4541"
      } ,
       "Https": {
        "Url": "https://0.0.0.0:4542",
        "Certificate": { 
          "Subject": "localhost", 
          "Store": "Root", 
          "Location": "CurrentUser", 
          "AllowInvalid": "true" 
      } 
     }
    }
  },
    "Auth": {
    "PublicAddress": ""
  },
  "Consent": {
    "Telemetry": false
  }
}

Public address and token issuer

• PublicAddress is where browsers and clients reach Pulse, as an https address with no path, for example https://pulse.example.com:4542. Empty sends each browser to the address its component uses for Pulse.
• The token issuer, the iss claim every token carries, is derived from it: the public address plus /auth, or with none set, Pulse's HTTPS endpoint plus /auth. It is not a setting of its own, and it has nothing to do with the issuer of a TLS certificate. Setting up Timebase Pulse explains why it has to be a real address.
• Changing the public address changes the issuer, so restart Pulse and then the other components, and expect users to sign in again.

Telemetry consent

Pulse is where every component's telemetry gathers before any of it leaves your site, and Consent:Telemetry decides whether it does. It ships off: each component's daily diagnostic counts and platform details reach Pulse and are discarded there. Set it to true and Pulse forwards them to Flow Software. Licence telemetry is the one exception and is sent either way, because the licence agreement depends on it.

• Telemetry is processed on your consent, so only you give it. Nothing in Timebase turns it on for you, and an upgrade keeps whatever you set.
• An administrator can change it from the interface: open Instance Info, then the Configuration card's settings editor, and switch Share telemetry under Telemetry. The card shows the current value.
• The change applies within five minutes, with no restart; Pulse reads the switch each time it drains what it has gathered.