12 Commits

Author SHA1 Message Date
1c0e9de289 Merge pull request 'docs: README for component/default/petclinic' (#9) from documentor-agent-component-default-petclinic-doc-7a878f6f8203 into main 2026-05-13 10:51:25 +00:00
eb74b27324 docs: generate README for component/default/petclinic [documentor-agent] 2026-05-13 10:51:21 +00:00
1e4eb91c10 Merge pull request 'docs: README for component/default/petclinic' (#8) from documentor-agent-component-default-petclinic-doc-52cb3f849f5f into main 2026-05-13 10:51:11 +00:00
66328cc005 docs: generate README for component/default/petclinic [documentor-agent] 2026-05-13 10:51:08 +00:00
9c74ca2ad1 Merge pull request 'docs: README for component/default/petclinic' (#7) from documentor-agent-component-default-petclinic-doc-ed08d1a43ef6 into main 2026-05-05 11:02:58 +00:00
2c64d74218 Merge pull request 'docs: README for component/default/petclinic-demo-jonathan-scaf-2' (#6) from documentor-agent-component-default-petclinic-demo-jonathan-scaf-2-doc-26eceb0fa4b9 into main 2026-05-05 11:02:58 +00:00
0aba4ac987 docs: generate README for component/default/petclinic [documentor-agent] 2026-05-05 11:02:54 +00:00
33b5b4506d docs: generate README for component/default/petclinic-demo-jonathan-scaf-2 [documentor-agent] 2026-05-05 11:02:53 +00:00
13426e0f99 Merge pull request 'docs: README for component/default/petclinic-demo-jonathan-scaf-2' (#5) from documentor-agent-component-default-petclinic-demo-jonathan-scaf-2-doc-d95bf65b5534 into main 2026-05-05 11:02:24 +00:00
2cc073baf5 docs: generate README for component/default/petclinic-demo-jonathan-scaf-2 [documentor-agent] 2026-05-05 11:02:21 +00:00
49c0442fff Merge pull request 'docs: README for component/default/petclinic' (#4) from documentor-agent-component-default-petclinic-doc-30fb4c9cd089 into main 2026-05-05 10:50:17 +00:00
e6065b0c5f docs: generate README for component/default/petclinic [documentor-agent] 2026-05-05 10:50:13 +00:00
2 changed files with 42 additions and 77 deletions

View File

@@ -1,7 +1,7 @@
---
title: "Petclinic Demo Jonathan Scaf 2"
generated_by: documentor-agent
generated_at: "2026-05-05T10:06:28+00:00"
generated_at: "2026-05-05T11:02:41+00:00"
human_edited: false
source_entity: "Component/default/petclinic-demo-jonathan-scaf-2"
source_repo: "https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2"
@@ -9,67 +9,61 @@ source_repo: "https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2
# Petclinic Demo Jonathan Scaf 2
> A deployment of the Spring PetClinic application, scaffolded via Backstage and managed with ArgoCD in the `demo-apps` namespace.
> A Spring Bootbased veterinary clinic application deployed via ArgoCD into the demo-apps namespace.
## Overview
Petclinic Demo Jonathan Scaf 2 is a deployment of the Spring PetClinic application, a sample Spring Boot project designed to showcase best practices in Java application development. This service was scaffolded using the Backstage Application Migration Factory template and integrates OpenTelemetry for observability, K6 for load testing, and Chaos Mesh for chaos engineering.
Petclinic Demo Jonathan Scaf 2 is a deployment of the Spring PetClinic application, a sample project showcasing Spring Boot capabilities. This service provides a web-based interface for managing veterinary clinic operations, including scheduling appointments, managing pet records, and tracking visits. It is designed to demonstrate modern application deployment practices, including GitOps workflows, OpenTelemetry instrumentation, and integration with Kubernetes.
The application provides a web interface for managing veterinary clinics, including features for scheduling appointments, managing pet records, and tracking clinic staff. It is deployed via ArgoCD, which continuously syncs the application from the `main` branch of its source repository into the `demo-apps` namespace.
This deployment is instrumented for monitoring and observability, with metrics and traces visualized in Grafana. It also supports rollback and automated sync workflows through ArgoCD.
The application is scaffolded using the Backstage Application Migration Factory template, which overlays CI/CD workflows and observability configurations. It is continuously deployed via ArgoCD, ensuring that changes pushed to the repository are automatically synced to the Kubernetes cluster.
## Repository
| Field | Value |
|---|---|
| Source Repo | [https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2](https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2) |
| Source Repo | [Petclinic Demo Jonathan Scaf 2](https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2) |
| Branch | main |
| ArgoCD App | petclinic-demo-jonathan-scaf-2 |
| Namespace | demo-apps |
## Architecture
- The application is based on the Spring PetClinic project, cloned from [https://github.com/spring-projects/spring-petclinic](https://github.com/spring-projects/spring-petclinic).
- OpenTelemetry auto-instrumentation is applied via Kustomize overlays, enabling detailed observability.
- The application is based on the Spring PetClinic project, cloned from `https://github.com/spring-projects/spring-petclinic`.
- OpenTelemetry auto-instrumentation is applied via Kustomize overlays, enabling detailed observability for traces, metrics, and logs.
- ArgoCD manages the deployment, continuously syncing changes from the `main` branch to the `demo-apps` namespace.
- The deployment flow includes CI workflows, Backstage catalog entity creation, and integration with monitoring tools like Grafana.
- The deployment flow includes CI workflows, Kubernetes manifests, and observability configurations integrated into the repository.
## Configuration
| Configuration | Description |
|---|---|
| `spring.profiles.active` | Specifies the active Spring profile (`mysql`, `postgres`, or default `h2`). |
| Database | Default is H2 in-memory; supports MySQL and PostgreSQL with Docker or Docker Compose. |
| OpenTelemetry | Auto-instrumentation enabled; traces exported to OTel Collector. |
| Database URLs | `jdbc:h2:mem:<uuid>` for H2, or Docker-based MySQL/PostgreSQL configurations. |
| OpenTelemetry Endpoint | `http://otel-collector.monitoring.svc.cluster.local:4318` |
## Operations
### Development Workflow
- **Development Workflow**:
```bash
git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git
cd petclinic-demo-jonathan-scaf-2
# make changes, then:
git add . && git commit -m "your change" && git push origin main
```
ArgoCD automatically syncs changes to the `demo-apps` namespace.
```bash
git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git
cd petclinic-demo-jonathan-scaf-2
# make changes, then:
git add . && git commit -m "your change" && git push origin main
```
- **Rollback**:
1. Open the [ArgoCD UI](https://argocd.kyndemo.live/applications/petclinic-demo-jonathan-scaf-2).
2. Click **History and Rollback**.
3. Select the desired revision and click **Rollback**.
Alternatively, revert the commit in Git and push — ArgoCD will auto-sync the rollback.
ArgoCD monitors the repository and automatically syncs changes to the `demo-apps` namespace.
### Rollback
1. Open the [ArgoCD UI](https://argocd.kyndemo.live/applications/petclinic-demo-jonathan-scaf-2).
2. Click **History and Rollback**.
3. Select the desired revision and click **Rollback**.
Alternatively, revert the commit in Git and push — ArgoCD will auto-sync the rollback.
<!-- TODO: FILL IN -->
## Observability
- **Grafana Dashboard**: [https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=petclinic-demo-jonathan-scaf-2](https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=petclinic-demo-jonathan-scaf-2)
- **OTel Collector Endpoint**: `http://otel-collector.monitoring.svc.cluster.local:4318`
Traces, metrics, and logs are exported to the OTel Collector and visualized in Grafana. Alerts are configured via Grafana and can be monitored in Backstage.
- **Grafana Dashboard**: [OpenTelemetry Application Observability](https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=petclinic-demo-jonathan-scaf-2)
- **Alerting**: Configured via Grafana with label selector `app.kubernetes.io/instance=petclinic-demo-jonathan-scaf-2`.
## Dependencies

View File

@@ -1,76 +1,47 @@
---
title: "Petclinic Service"
title: "Petclinic"
generated_by: documentor-agent
generated_at: "2026-05-05T10:41:37+00:00"
generated_at: "2026-05-13T10:51:15+00:00"
human_edited: false
source_entity: "Component/default/petclinic"
source_repo: "https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2"
source_repo: "https://gitea.kyndemo.live/validate/petclinic-demo-andrej2"
---
# Petclinic Service
# Petclinic
> A Spring Bootbased application for managing veterinary clinic operations, including scheduling, customer management, and pet records.
> Petclinic service — part of petclinic-demo-andrej2.
## Overview
The Petclinic service is a Java-based application built using Spring Boot. It provides a comprehensive solution for managing veterinary clinic operations, including scheduling appointments, managing customer and pet records, and handling clinic workflows. Originally developed as a sample application by the Spring community, this service has been adapted and deployed as part of the `petclinic-demo-jonathan-scaf-2` system.
The application supports multiple database configurations, including in-memory H2, MySQL, and PostgreSQL, and is designed to be easily deployable in containerized environments. It includes OpenTelemetry instrumentation for observability and integrates with ArgoCD for continuous deployment. The service plays a critical role in the broader veterinary platform, serving as the primary interface for clinic management.
The Petclinic service is a core component of the petclinic-demo-andrej2 system. It is designed to provide functionality for managing pet-related data and operations, such as scheduling appointments, tracking pet health records, and managing customer information. This service is built using Java and integrates with various platform tools for deployment, observability, load testing, and chaos engineering.
## Repository
| Field | Value |
|---|---|
| Source Repo | [Petclinic Repository](https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2) |
| Branch | main |
| ArgoCD App | petclinic-demo-jonathan-scaf-2 |
| Namespace | demo-apps |
| Field | Value |
|---------------|-------------------------------------------------------------------------------------------|
| Source Repo | [Petclinic Repository](https://gitea.kyndemo.live/validate/petclinic-demo-andrej2) |
| Branch | main |
| ArgoCD App | petclinic-demo-andrej2 |
| Namespace | demo-apps |
## Architecture
- The Petclinic service is scaffolded using the Application Migration Factory Backstage template.
- Deployment flow:
1. Source code cloned from the original Spring Petclinic repository.
2. Backstage overlays applied for catalog entity creation and CI workflows.
3. OpenTelemetry auto-instrumentation injected via Kustomize overlays.
4. ArgoCD Application created targeting the `demo-apps` namespace.
5. Continuous sync from the `main` branch via ArgoCD.
- Observability is enabled through OpenTelemetry, with metrics and traces visualized in Grafana.
<!-- TODO: FILL IN -->
## Configuration
| Configuration | Description |
|---|---|
| `spring.profiles.active` | Sets the active Spring profile (`mysql`, `postgres`, or default `h2`). |
| Database URL | For H2: `jdbc:h2:mem:<uuid>` (printed at startup). |
| MySQL Docker | `docker run -e MYSQL_USER=petclinic -e MYSQL_PASSWORD=petclinic -e MYSQL_ROOT_PASSWORD=root -e MYSQL_DATABASE=petclinic -p 3306:3306 mysql:9.6` |
| PostgreSQL Docker | `docker run -e POSTGRES_USER=petclinic -e POSTGRES_PASSWORD=petclinic -e POSTGRES_DB=petclinic -p 5432:5432 postgres:18.3` |
<!-- TODO: FILL IN -->
## Operations
- **Local Development**:
1. Clone the repository: `git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git`.
2. Start the application using Maven: `./mvnw spring-boot:run` or Gradle: `./gradlew bootRun`.
3. Access the application at `http://localhost:8080`.
- **Container Build**:
Use the Spring Boot build plugin: `./mvnw spring-boot:build-image`.
- **Rollback**:
1. Open the [ArgoCD UI](https://argocd.kyndemo.live/applications/petclinic-demo-jonathan-scaf-2).
2. Use the "History and Rollback" feature to revert to a previous version.
<!-- TODO: FILL IN -->
## Observability
- **Grafana Dashboard**: [OpenTelemetry Application Observability](https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-service=petclinic).
- **OTel Collector Endpoint**: `http://otel-collector.monitoring.svc.cluster.local:4318`.
- **Alerts**: Configured via Grafana with label selector `app=petclinic`.
- [Grafana Dashboard](https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-service=petclinic)
## Dependencies
- `component:default/argocd-service`
- `resource:default/k6-operator`
- `resource:default/otel-collector`
- `resource:default/veterinary-platform`
- `resource:default/otel-collector`