Project Platform Application Dependencies
![](../../__attachments/143696348/enterprise%20-%20badge@500w.png?inst-v=fbc98f0a-f9ae-4d4c-828f-dc0defe966ca)
Dependencies between project platform applications
There are many dependencies between the applications that are deployed to a project’s attached clusters. It is important to note these dependencies when customizing the platform applications to ensure that your services are properly deployed to the clusters. For more information on how to customize platform applications, see Platform Application Deployment.
Application Dependencies
When deploying or troubleshooting applications, it helps to understand how applications interact and may require other applications as dependencies.
If an application’s dependency does not successfully deploy, the application requiring that dependency does not successfully deploy.
The following sections detail information about the platform applications.
Logging
Collects logs over time from Kubernetes pods deployed in the project namespace. Also provides the ability to visualize and query the aggregated logs.
project-logging: Defines resources for the Logging Operator which uses them to direct the project’s logs to its respective Grafana Loki application.
project-grafana-loki: A horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus.
project-grafana-logging: Logging dashboard used to view logs aggregated to Grafana Loki.
The project logging applications depend on the workspace logging applications being deployed.
Application | Dependencies |
---|---|
project-logging | logging-operator (workspace) |
project-grafana-loki | project-logging, grafana-loki (workspace), logging-operator (workspace) |
project-grafana-logging | project-grafana-loki |