Skip to content

Latest commit

 

History

History
18 lines (12 loc) · 4.63 KB

configuration-options.md

File metadata and controls

18 lines (12 loc) · 4.63 KB
description
All available deployment options for ux4iot

Configuration Options

You can generally deploy a ux4iot without specifying any parameters, except for the iotHubEventHubConnectionString. This is because we provide default values for all other configuration variables. However we highly recommend setting a serverVersion. Without it you will deploy the latest code version which is basically a version of a single commit. You will use a development version of ux4iot then.

The configuration options are somewhat ordered by priority. You will need the last ones the least amount of time. We recommend to deploy a ux4iot service with at least the following configuration variables:

  • serverVersion
  • iotHubEventHubConnectionString
  • iotHubServiceConnectionString
  • eventHubConsumerGroup
  • sku
Bicep / ARM ParameterDefault ValueDescriptionAllowed Valuestype
serverVersionlatestux4iot docker image version to deployinfra
iotHubEventHubConnectionStringThe connection string of the EventHub that publishes data you want to subscribe toserver
iotHubServiceConnectionString""The service connection string of the IoTHub you want to access for devices. You need to pick a connection string that includes the policies "Registry Read" and "Service Connect"server
eventHubConsumerGroup$DefaultThe consumer group of the EventHub that publishes data you want to subscribe toserver
skustandardThe scaling tier of ux4iot. Influences cpu and memory of ux4iot and redis containers within the container app.

Standard:
cpu cores redis: 0.5
memory redis: 1Gi
cpu cores ux4iot: 1.0
memory ux4iot: 2Gi

Small:
cpu cores redis: 0.25
memory redis: 0.5Gi
cpu cores ux4iot: 0.5
memory ux4iot: 1Gi
standard | smallinfra
throttlingInterval-1Throttle time to delay messages put on the websocket for consumers in milliseconds.server
connectionStateCacheTTL60Time how long a connection state update is persisted in the internal ux4iot cache, in seconds. Set to -1 set the lifetime to infinity.server
customTimestampKey_tsCustom object key of a message to look for the timestampserver
customDeviceIdKeydeviceIdCustom object key of a message to look for the deviceIdserver
customConnectionStateKey""Custom object key of a message to look for the connectionState.server
connectionStateOnTelemetrytrueFlag on whether the connection state of a device should be updated whenever a telemetry message for that device is received.true | falseserver
logLevelinfoSets the initial log level of ux4ioterror | warn | info | verbose | debugserver
locationresourceGroup().locationThe location where all resources of ux4iot should be deployedinfra
logAnalyticsTracesTableTierAnalyticsTier of the log analytics traces table. You can only change this value once a week, as dictated by microsoft.
Basic Tier will give you less options when querying for logs, but is cheaper. Also the retention time will be set to 7 days instead of 90.
Basic | Analyticsinfra
redisVersion1.2.0redis docker image version to deployinfra
skipCustomResourcefalseSkips deployment of the internal function app for the custom resource providertrue | falseinfra
skipKeyVaultContentsfalseSkips deployment of key vault secrets, which leads to the update of the iotHubServiceConnectionStringSecret, iotHubEventHubConnectionStringSecret, storageAccountConnectionStringSecret, backendFuncTriggerUrlSecrettrue | falseinfra
primaryAdminSecret""Primary Shared Access Key of the Ux4iotinfra
secondaryAdminSecret""Secondary Shared Access Key of the Ux4iotinfra