# Monitoring in ONEWEB Monitoring is an essential part of the **ONEWEB architecture**, especially in cloud and distributed environments.\ It provides visibility into both **infrastructure health** and **platform service behavior**, enabling proactive operations and faster issue resolution. To support monitoring across the platform, **ONEWEB uses the ELK Stack** as the foundation for collecting, analyzing, and visualizing operational data. *** #### Monitoring Architecture Overview Within the ONEWEB architecture, monitoring serves as a **cross‑cutting capability** that spans multiple layers, including: * Cloud or on‑premises infrastructure * Platform services and runtimes * Containerized components (in cloud deployments) * Application‑level logs and events By aggregating data from these layers, ONEWEB enables centralized monitoring and observability across environments. *** #### ELK Stack as the Monitoring Foundation ONEWEB adopts the **ELK Stack** to support log aggregation, analysis, and visualization for both infrastructure and platform services. {% hint style="info" %} **ELK** is an acronym for three open‑source projects: * **Elasticsearch** – A distributed search and analytics engine used to store and query log and metric data * **Logstash** – A server‑side data processing pipeline that ingests data from multiple sources, transforms it, and forwards it to Elasticsearch * **Kibana** – A visualization layer that provides dashboards, charts, and analytics based on data stored in Elasticsearch Together, the ELK Stack enables centralized log aggregation, operational analysis, and visual monitoring of systems and applications. {% endhint %} *** #### What Monitoring Enables in ONEWEB By using the ELK Stack, ONEWEB provides the ability to: * Aggregate logs from platform services and infrastructure components * Analyze system behavior and application activity * Visualize metrics and logs through dashboards and charts * Support faster troubleshooting and root‑cause analysis * Enable security analysis and operational insights This monitoring capability is especially important in **High Availability** and **Cloud Architecture** deployments, where multiple components operate in a distributed manner. *** #### Role of Monitoring in Design ONEWEB Architecture From an architectural perspective: * **Deployment Architecture** defines where components run * **Server Configuration** defines which platform capabilities are deployed * **Container Structure** defines how components are packaged and orchestrated * **Monitoring Architecture** provides visibility across all of these layers Monitoring ensures that the ONEWEB platform remains observable, manageable, and reliable as system complexity grows. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.onewebstack.com/oneweb-platform-th/getting-started/installation-guide/plan-your-oneweb-installation/design-oneweb-architecture/monitoring-in-oneweb.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.