platform-docs/catalog/component/default/petclinic/README.md

title, generated_by, generated_at, human_edited, source_entity, source_repo

title	generated_by	generated_at	human_edited	source_entity	source_repo
Petclinic Service	documentor-agent	2026-05-13T10:51:17+00:00	false	Component/default/petclinic	https://gitea.kyndemo.live/validate/petclinic-demo-andrej2

Petclinic Service

A Spring Boot application for managing veterinary clinics, including scheduling, customer management, and pet records.

Overview

The Petclinic service is a Spring Boot application designed to manage veterinary clinic operations. It provides features such as scheduling appointments, managing customer and pet records, and viewing clinic information. Originally developed as a sample application by the Spring community, this service has been adapted and deployed using Backstage templates for enhanced observability and deployment automation.

The application supports multiple database configurations, including in-memory H2, MySQL, and PostgreSQL, and can be run locally or deployed in containerized environments. It is instrumented with OpenTelemetry for comprehensive observability and integrates with Grafana for monitoring and alerting.

Repository

Field	Value
Source Repo	Petclinic Repository
Branch	main
ArgoCD App	petclinic-demo-andrej2
Namespace	demo-apps

Architecture

• The service is scaffolded using the Backstage Application Migration Factory template.
• Deployment is managed via ArgoCD, which continuously syncs the main branch to the demo-apps namespace.
• OpenTelemetry auto-instrumentation is applied via Kustomize overlays, enabling detailed traces, metrics, and logs.
• The application supports multiple database configurations, including H2 (default), MySQL, and PostgreSQL, with profiles for each database type.
• Observability is integrated with Grafana, providing dashboards and alerts for monitoring service health and performance.

Configuration

Configuration	Description
spring.profiles.active	Sets the active Spring profile (mysql, postgres, or default h2).
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

Local Development

1. Clone the repository:

   git clone https://gitea.kyndemo.live/validate/petclinic-demo-andrej2.git
   cd petclinic-demo-andrej2
   

2. Run the application:
   • Using Maven:

     ./mvnw spring-boot:run
     

   • Using Gradle:

     ./gradlew bootRun
     

3. Access the application at http://localhost:8080.

Deployment

Changes pushed to the main branch are automatically synced to the demo-apps namespace by ArgoCD. To roll back, use the ArgoCD UI or revert the commit in Git.

Database Setup

• Default: In-memory H2 database.
• Persistent options: MySQL or PostgreSQL, with Docker or docker-compose configurations.

Rollback

1. Open the ArgoCD UI.
2. Select History and Rollback.
3. Choose the desired revision and click Rollback.

Observability

• Grafana Dashboard: View Dashboard
• Alerts: Configured via Grafana, filter by app=petclinic.
• OpenTelemetry instrumentation is enabled for traces, metrics, and logs.

Dependencies

• component:default/argocd-service
• resource:default/k6-operator
• resource:default/otel-collector