Tree:
bbdfc416ca
AlexDoanTB-patch-1
_tbel_fix_bug_tb_date_timezone_pattern
bug/update-service-content-type
bug/yml-change-check
coap_dtls
copilot/fix-protobuf-field-names
copilot/sub-pr-14760
domains
edqs-grafana
feature/alarm-count-query
feature/basic-widget-config
feature/cf-merge-function
feature/cfs
feature/cn-locale-improvements
feature/controller-logging
feature/deduplication-node
feature/device-library
feature/edqv2
feature/firmware-footprint
feature/home-page
feature/html-container-widget
feature/iot-hub
feature/iot-hub-item-link
feature/lts-4.3-iot-hub
feature/lts-4.3-iot-hub-alarm-rules
feature/menu-refactoring
feature/proto
feature/queries-not-option
feature/queue-consumer-manager
feature/rate-limits-notifications
feature/rpc-monitoring-lts-4.2
feature/rule-node-cache
feature/serialization
feature/sticky-partitioning
feature/sub-service-improvement
feature/tb-event
feature/tenant-export
feature/user-notification-settings
feature/user-settings
feature/websocket-rpc
feature/widget-bundles
fix/activity-notification
fix/alarm-propagation
fix/alarm-rules-doc
fix/gradle-warning-mode-parallel-timeout
fix/msa-tests-log
fix/openapi-spec
fix/rest-api-call-node-blocking-actor-thread
fix_bug_coap_tests
fix_bug_copas_Access_Token_DTLS
fix_bug_tbDate_Object_mapper
fix_bug_transactional_other_entity_with_tests
gh-protection-test
hotfix
improvement/ws/sanitized
improvements/isolated-queues
improvements/tb-upgrade
lts-4.2
lts-4.3
lts-4.3-rc
lts-patch-system-images
lwm2m_fix_bug_null_point_profileleid_after_sleep_master
master
msa-cfs-tests-trace-logs
oauth2_refactoring
rc
rc-4.1.1
release-1.0
release-1.1
release-1.2
release-1.3
release-1.4
release-2.0
release-2.2
release-2.3
release-2.4
release-2.5
release-3.0
release-3.1
release-3.2
release-3.3
release-3.3-CVE-2022-22965
release-3.4
release-3.5
release-3.6
release-3.7
release-3.8
release-3.9
release-4.0
release-4.1
release-4.2
release-4.3
sparkplag_Telemetry
sparkplug-any-name-node-unique-device-names
sparkplug-any-name-node-unique-device-names_temp
system-params-js-evaluator
tbel_encodeUri
test_suite_testcontaihers_2_02
vb-master
vb-rc
wire-schema-replacement
v1.0
v1.0.1
v1.0.2
v1.0.3
v1.1
v1.2
v1.2.1
v1.2.2
v1.2.3
v1.3
v1.3.1
v1.4
v2.0
v2.0.1
v2.0.2
v2.0.3
v2.1
v2.1.1
v2.1.2
v2.1.3
v2.2
v2.3
v2.3.1
v2.4
v2.4.1
v2.4.2
v2.4.2.1
v2.4.3
v2.5
v2.5.1
v2.5.2
v2.5.3
v2.5.4
v2.5.5
v2.5.6
v3.0
v3.0.1
v3.1
v3.1.1
v3.2
v3.2.1
v3.2.2
v3.3
v3.3.1
v3.3.2
v3.3.3
v3.3.4
v3.3.4.1
v3.4
v3.4.1
v3.4.2
v3.4.3
v3.4.4
v3.5
v3.5.1
v3.6
v3.6.1
v3.6.2
v3.6.3
v3.6.4
v3.7
v3.8
v3.8.1
v3.9
v3.9.1
v4.0
v4.0.1
v4.0.2
v4.1
v4.2
v4.2.1
v4.2.1.1
v4.2.1.2
v4.2.2
v4.2.2.1
v4.2.2.2
v4.3
v4.3.0.1
v4.3.1
v4.3.1.1
v4.3.1.2
${ noResults }
2 Commits (bbdfc416ca38588dec6b282c7ca6da9c1dd08e98)
| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
8aef432958 |
docs(monitoring): document RPC monitoring config and behaviour (#15541)
- tb-monitoring.yml: add the optional rpc.{enabled,request_timeout_ms}
sub-block to every transport target with comments explaining the
per-transport mechanism, plus a commented-out secure-MQTT example
- monitoring/src/main/resources/README.md: new file with the YAML key
table, a per-transport behaviour summary, the failure-attribution
semantics (RpcInfo => "<transport> RPC"), and troubleshooting notes
including the rpc.request_timeout_ms < monitoring.rest.request_timeout_ms
ordering constraint
- 2026-04-29-rpc-monitoring-design.md: update §5 to list MQTT + HTTP +
CoAP + LwM2M as shipped phases (replacing the previous "MQTT only +
follow-ups" framing), reword §6 open decisions as resolved decisions
with all four transports in scope, add §4.6 explaining the LwM2M
Read-vs-echo asymmetry and the conservative 6000 ms default
|
1 month ago |
|
|
4d4a6d0dcd |
docs(monitoring): RPC monitoring design (rc baseline)
Adds an opt-in two-way RPC companion check to each transport target so
the monitoring loop covers the cloud-to-device direction (REST → rule
engine → transport → device → response), not just the uplink.
The shape mirrors how the calculated_fields flag layers an extra
assertion onto the existing telemetry check today: same loop, same
auto-provisioned device, same MQTT client (also subscribes the RPC
topic when rpc.enabled), one extra round-trip per cycle. Failure
attribution flows through MonitoringReporter unchanged, so RPC
failures appear as their own row in the IncidentManager header
("MQTT RPC") alongside the transport row.
Includes ASCII + mermaid diagrams of the current and proposed flows,
a sequence diagram of the round-trip, an incident-attribution table,
phased implementation plan, and open decisions.
|
1 month ago |