Documentation: Flowy Troubleshooting
Identify versions in use
Using a GET API call you can identify the precise versions you're currently using:
- Processing:
/actuator/info
- Admin:
/api/actuator/info
Timeout handling
It is crucial to understand that timeouts can be set on different levels and that they need to be carefully aligned - most importantly on process level. This timeout is only checked after the completion of each step. This has to be considered if i.e. an slow SMTP server is being used within an SMTP step.
Prometheus/Grafana usage
Prometheus is fully supported, please refer to the Flowy Configuration configuration for details on how to whitelist the IP addresses. Furthermore, the two following actuators need to be configured within prometheus.yml
:
- job_name: 'QA processing'
scheme: https
metrics_path: '/actuator/prometheus'
scrape_interval: 5s
static_configs:
- targets: [ '<your-processing-host>' ]
labels:
instance: 'qa'
application: 'processing'
- job_name: 'Flowy Admin'
scheme: https
metrics_path: '/api/actuator/prometheus'
scrape_interval: 5s
static_configs:
- targets: [ '<your-admin-host>' ]
labels:
instance: 'qa'
application: 'admin'