Why Use Persistent Capsule IDs?
By default, any change to a capsule—such as its start time, end time, or properties—will cause it to be treated as a distinct capsule, even if it represents the same logical event, such as an alarm or batch. This behavior can disrupt user workflows that rely on stable capsule references.
InfluxDB V2
{
"Url" : "http://localhost:8086",
"Username" : "admin",
"Password" : "admin",
"Token" : null,
"ConnectTimeoutInSeconds" : 30,
"ReadTimeoutInSeconds" : 120,
"CallTimeoutInSeconds" : 150,
"Organizations" : [ ],
"Simulation" : false,
"IndexingSchemaQueryStart" : null,
"IndexingSchemaQueryStop" : null,
"IndexingSchemaDiscoverOnly" : false
}
InfluxDB V2 Additional Configuration
|
Property Name |
Default Value |
Data Type |
Description |
|---|---|---|---|
|
|
|
String |
The URL of the InfluxDB v2 server you wish to connect to. If you are using InfluxDB Cloud, this is the root of the URL you will see in your browser address bar when using the web-based admin console (e.g.: |
|
|
|
String |
NOT RECOMMENDED: This is the username of a user that has access to InfluxDB. It is strongly recommended that you commission an API Token and use that instead, as described here: https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/. You will place the token string in the |
|
|
|
String/SecretFile |
NOT RECOMMENDED: The password of a user that has access to the database. It is recommended to leverage a Secrets File to store this information. It is strongly recommended that you commission an API Token and use that instead, as described here: https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/. You will place the token string in the |
|
|
null |
String/SecretFile |
The API Token used to access InfluxDB. Follow the instructions at https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/ to generate your token. It is recommended to leverage a Secrets File to store this information. You can also authenticate via username / password, but it is not recommended. |
|
|
30 |
Integer |
The connect timeout is applied when connecting a TCP socket to the target host. |
|
|
120 |
Integer |
The read timeout is applied to both the TCP socket and for individual read IO operations including on Source of the Response. |
|
|
150 |
Integer |
The call timeout spans the entire call: resolving DNS, connecting, writing the request body, server processing, and reading the response body. If the call requires redirects or retries they must all be completed within one timeout period. |
|
|
Empty List |
List of Organizations |
Seeq will automatically fill in this property on the first connection. Afterward, you may modify the organization definition as specified in Rearranging the Asset Tree. |
|
|
|
Boolean |
If you have a blank InfluxDB server and you're just experimenting, you can load simulated data into InfluxDB by changing this field to |
|
|
null (30 days ago) |
String |
InfluxDB v2 requires that a time period is included when querying for the set of measurements / tag keys / field keys that are present in a bucket. When this field is set to null, a default of 30 days ago is used. If you find that “old” measurements/tags/fields are not being indexed, considering setting this field to |
|
|
null (now) |
String |
InfluxDB v2 requires that a time period is included when querying for the set of measurements / tag keys / field keys that are present in a bucket. When this field is set to null, a default of “now” is used. |
|
|
|
Boolean |
If set to |