Overview
In OctoMesh, we understand that data is at the heart of your operations. This chapter focuses on how you can access and interact with your data through our Construction Kits (CK), tailored for both runtime data and stream (time series) data. Leveraging GraphQL endpoints, OctoMesh offers a seamless and efficient way to work with your data, regardless of its nature.
- Construction Kit (CK): At the foundation of data modeling within OctoMesh lies Construction Kit (CK). It provides a flexible and robust framework for defining data types and attributes, enabling structured and comprehensive data modeling. To dive deeper into CK and its capabilities, please visit ConstructionKits.
- Runtime Model (RT Model): Runtime Model consists of a collection of Runtime entities, that are instances of Construction Kit Types. Runtime entities remains constant until an external action modifies it. This category includes configurations, metadata, and other data types that do not change over time on their own. Accessing runtime data is facilitated through GraphQL endpoints, providing a robust querying capability.
- Stream Data: Stream Data captures the essence of time series, real-time, or event data that evolves over time. Examples include sensor readings, user interactions, or live financial data. Like runtime data, stream data is accessible via GraphQL endpoints, ensuring consistency in how data is queried within OctoMesh.
Accessing data
You can explore the GraphQL API via the GraphQL playground. The URI depend on your installation type and tenant you are using. The best way is to use the AdminPanel. Depending on your environment for example under an url like the following: https://localhost:5001/tenants/meshtest/graphql/playground. In this case the tenant is called meshtest.
Below is an example query designed to fetch runtime data specific to an energy meter within the industry energy domain. This query illustrates how to retrieve the runtime ID, type ID, and name of the entity.