You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/admin.md
+39-5Lines changed: 39 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,9 +125,9 @@ allowing the computer to interpret the rest of the data with more clarity and de
125
125
```
126
126
127
127
Under mixed mode, **NGSI v2** payloads are used for context broker communications by default, but this payload may also
128
-
be switched to **NGSI LD** at group or device provisioning time using the `ngsiVersion` field in the
129
-
provisioning API. The `ngsiVersion` field switch may be added at either group or device level, with the device level
130
-
overriding the group setting.
128
+
be switched to **NGSI LD** at group or device provisioning time using the `ngsiVersion` field in the provisioning API.
129
+
The `ngsiVersion` field switch may be added at either group or device level, with the device level overriding the group
130
+
setting.
131
131
132
132
#### `server`
133
133
@@ -306,7 +306,8 @@ added `agentPath`:
306
306
307
307
#### `types`
308
308
309
-
This parameter includes additional groups configuration as described into the [Config group API](api.md#config-group-api) section.
309
+
This parameter includes additional groups configuration as described into the
310
+
[Config group API](api.md#config-group-api) section.
310
311
311
312
#### `service`
312
313
@@ -415,7 +416,38 @@ IotAgents, as all Express applications that use the body-parser middleware, have
415
416
size that the application will handle. This default limit for ioiotagnets are 1Mb. So, if your IotAgent receives a
416
417
request with a body that exceeds this limit, the application will throw a “Error: Request entity too large”.
417
418
418
-
The 1Mb default can be changed setting the `expressLimit` configuration parameter (or equivalente `IOTA_EXPRESS_LIMIT` environment variable).
419
+
The 1Mb default can be changed setting the `expressLimit` configuration parameter (or equivalente `IOTA_EXPRESS_LIMIT`
420
+
environment variable).
421
+
422
+
#### `storeLastMeasure`
423
+
424
+
If this flag is activated, last measure arrived to Device IoTAgent without be processed will be stored in Device under
425
+
`lastMeasure` field (composed of sub-fields `timestamp` and `measure` for the measure itself, in multi-measure format).
426
+
This flag is overwritten by `storeLastMeasure` flag in group or device. This flag is disabled by default.
427
+
428
+
For example in a device document stored in MongoDB will be extended with a subdocument named lastMeasure like this:
429
+
430
+
```json
431
+
{
432
+
"lastMeasure": {
433
+
"timestamp": "2025-01-09T10:35:33.079Z",
434
+
"measure": [
435
+
[
436
+
{
437
+
"name": "level",
438
+
"type": "Text",
439
+
"value": 33
440
+
}
441
+
]
442
+
]
443
+
}
444
+
}
445
+
```
446
+
447
+
#### `useCBflowControl`
448
+
449
+
If this flag is activated, when iotAgent invokes Context Broker will use [flowControl option](https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/admin/perf_tuning.md#updates-flow-control-mechanism). This flag is overwritten by
450
+
`useCBflowControl` flag in group or device. This flag is disabled by default.
Copy file name to clipboardExpand all lines: doc/api.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1777,6 +1777,8 @@ Config group is represented by a JSON object with the following fields:
1777
1777
|`payloadType`| ✓ | string || optional string value used to switch between **IoTAgent**, **NGSI-v2** and **NGSI-LD** measure payloads types. Possible values are: `iotagent`, `ngsiv2` or `ngsild`. The default is `iotagent`. |
1778
1778
|`transport`| ✓ |`string`|| Transport protocol used by the group of devices to send updates, for the IoT Agents with multiple transport protocols. |
1779
1779
|`endpoint`| ✓ |`string`|| Endpoint where the group of device is going to receive commands, if any. |
1780
+
|`storeLastMeasure`| ✓ |`boolean`|| Store in device last measure received. See more info [in this section](admin.md#storelastmeasure). False by default |
1781
+
|`useCBflowControl`| ✓ |`boolean`|| Use Context Broker flow control. See more info [in this section](admin.md#useCBflowControl). False by default |
1780
1782
1781
1783
### Config group operations
1782
1784
@@ -1996,8 +1998,10 @@ the API resource fields and the same fields in the database model.
1996
1998
|`internal_attributes`| ✓ |`array`|| List of internal attributes with free format for specific IoT Agent configuration. |
1997
1999
|`explicitAttrs`| ✓ |`boolean`| ✓ | Field to support selective ignore of measures so that IOTA doesn’t progress. See details in [specific section](#explicitly-defined-attributes-explicitattrs)|
1998
2000
|`ngsiVersion`| ✓ |`string`|| string value used in mixed mode to switch between **NGSI-v2** and **NGSI-LD** payloads. The default is `v2`. When not running in mixed mode, this field is ignored. |
1999
-
|`payloadType`| ✓ |`string`|| optional string value used to switch between **IoTAgent**, **NGSI-v2** and **NGSI-LD** measure payloads types. Possible values are: `iotagent`, `ngsiv2` or `ngsild`. The default is `iotagent`. |
2000
-
2001
+
|`payloadType`| ✓ |`string`|| optional string value used to switch between **IoTAgent**, **NGSI-v2** and **NGSI-LD** measure payloads types. Possible values are: `iotagent`, `ngsiv2` or `ngsild`. The default is `iotagent`. |
2002
+
|`storeLastMeasure`| ✓ |`boolean`|| Store in device last measure received. See more info [in this section](admin.md#storelastmeasure). False by default. |
2003
+
|`lastMeasure`| ✓ |`object`|| last measure stored on device when `storeLastMeasure` is enabled. See more info [in this section](admin.md#storelastmeasure). This field can be cleared using `{}` in a device update request. In that case, `lastMeasure` is removed from device (until a next measure is received and `lastMesuare` gets created again). |
2004
+
|`useCBflowControl`| ✓ |`boolean`|| Use Context Broker flow control. See more info [in this section](admin.md#useCBflowControl). False by default. |
0 commit comments