-
Notifications
You must be signed in to change notification settings - Fork 6
Created Test-Things Architecture Diagram #64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Created Test-Things Architecture Diagram #64
Conversation
I noticed an issue with your Eclipse Contributor Agreement which you need to sign first before being able to push content. see also https://api.eclipse.org/git/eca/status/gh/eclipse-thingweb/test-things/64 |
@@ -16,6 +16,16 @@ The protocols you can currently test are: | |||
- CoAP | |||
- MQTT | |||
- Modbus | |||
 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as mentioned in the call, please add a title above this or move the diagram under "How It Works"
|
||
## How It Works | ||
|
||
- External applications—known as WoT Consumer Stacks—connect to the system. Traefik, which handles inbound HTTP requests, or a MQTT broker for real-time, event-based communication allow them to communicate with the internal services ("Things") in two main methods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- External applications—known as WoT Consumer Stacks—connect to the system. Traefik, which handles inbound HTTP requests, or a MQTT broker for real-time, event-based communication allow them to communicate with the internal services ("Things") in two main methods. | |
- External applications —known as WoT Consumer Stacks— send requests to the Things. Traefik, which handles inbound HTTP requests, or an MQTT broker allow them to communicate with the internal services ("Things") in two main methods. |
- The primary application services, the "Things" (A, B, C, D) reflect several functionalities like those of a Coffee Machine or Elevator. Every service is specified by a Thing Description (TD), a standardized metadata file that explains the service's capabilities and how to interact with it. | ||
- **Monitoring and Observability:** The system is built up comprehensively for monitoring. | ||
- Promtail collects logs from the services and sends them to Loki, a log aggregation system. | ||
- Prometheus, a time-series database, stores container performance measurements that cAdvisor gathers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mention what is cAdvisor first
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please make the figure more compact, i.e. the top and bottom part of the cloud is not needed
Added the architecture diagram for the test-things repository. Included the 4 things, how they interact with each other, and how the developer and the end user can interact with them.