Skip to main content

​
Deploy Monitoring

Deploy monitoring and observability services for ORISO Platform. Monitoring components are deployed via Helm as part of the oriso-platform umbrella chart.
Monitoring components:
  • SignOZ - Observability platform (APM, tracing, metrics)
  • Health Dashboard - Service health monitoring
  • Status Page - Public status page
1

Verify Monitoring Deployment

Monitoring services should already be deployed via Helm. Verify all components are running.
# Check monitoring pods
kubectl get pods -n caritas | grep -E "signoz|health|status"

# Check SignOZ (if deployed in platform namespace)
kubectl get pods -n platform | grep signoz

# Check Health Dashboard
kubectl get pods -n caritas | grep health-dashboard
Monitoring pods should be running. If not, they may need to be enabled in Helm values.
2

Deploy SignOZ (Optional)

Deploy SignOZ observability platform using Helm.
SignOZ provides distributed tracing, metrics, and logs. It’s deployed in the platform namespace.
# Add SignOZ Helm repo
helm repo add signoz https://charts.signoz.io
helm repo update

# Create namespace
kubectl create namespace platform

# Install SignOZ
cd ~/online-beratung/caritas-workspace/ORISO-SignOZ
helm install signoz signoz/signoz \
  --namespace platform \
  --values signoz-values-current.yaml

# Wait for SignOZ (may take 5-10 minutes)
kubectl wait --for=condition=ready pod \
  -l app.kubernetes.io/instance=signoz \
  -n platform \
  --timeout=600s

# Get SignOZ URL
kubectl get svc -n platform signoz-frontend
SignOZ pods should be running. Access at http://91.99.219.182:3001
3

Verify Health Dashboard

Health Dashboard monitors all service health endpoints.
# Check Health Dashboard pod
kubectl get pods -n caritas | grep health-dashboard

# Check service
kubectl get svc -n caritas | grep health-dashboard

# Access Health Dashboard
curl -I http://91.99.219.182:9001
Health Dashboard:
  • URL: http://91.99.219.182:9001
  • Checks: All /actuator/health endpoints every 60 seconds
  • Service: oriso-platform-health-dashboard.caritas.svc.cluster.local:9001
4

Configure Service Monitoring

Configure services to export metrics to SignOZ (optional).For Spring Boot Services:Add OpenTelemetry Java agent to service deployment:
# In Helm values or deployment
env:
- name: JAVA_TOOL_OPTIONS
  value: >-
    -javaagent:/opt/otel/opentelemetry-javaagent.jar
    -Dotel.service.name=userservice
    -Dotel.exporter.otlp.endpoint=http://signoz-otel-collector.platform.svc.cluster.local:4317
    -Dotel.exporter.otlp.protocol=grpc
Download OpenTelemetry Agent:
wget https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar

​
Monitoring Components

​
SignOZ

  • Namespace: platform
  • Access: http://91.99.219.182:3001
  • Credentials: caritas@gmail.com / @Caritas1234
  • Components:
    • SignOZ Backend
    • ClickHouse (time-series DB)
    • OTEL Collector
  • Features:
    • Distributed tracing
    • Metrics collection
    • Log aggregation
    • APM dashboards

​
Health Dashboard

  • Namespace: caritas
  • Service: oriso-platform-health-dashboard
  • Access: http://91.99.219.182:9001
  • Features:
    • Real-time health checks
    • Service status monitoring
    • Historical health data
    • Manual refresh capability

​
Status Page

​
Access URLs

After deployment, access monitoring at:

​
Troubleshooting

​
SignOZ Not Starting

# Check pods
kubectl get pods -n platform

# Check logs
kubectl logs -n platform -l app.kubernetes.io/instance=signoz

# Check resources
kubectl top pods -n platform

​
Health Dashboard Not Working

# Check pod
kubectl get pods -n caritas | grep health-dashboard

# Check logs
kubectl logs -n caritas deployment/oriso-platform-health-dashboard

# Verify service endpoints are accessible
kubectl exec -n caritas deployment/oriso-platform-health-dashboard -- \
  curl http://oriso-platform-userservice.caritas.svc.cluster.local:8082/actuator/health

​
Metrics Not Appearing in SignOZ

# Check OTEL collector
kubectl get pods -n platform | grep otel-collector

# Check collector logs
kubectl logs -n platform -l app=otel-collector

# Verify service has OpenTelemetry agent
kubectl exec -n caritas deployment/oriso-platform-userservice -- env | grep OTEL

​
Next Steps