This guide walks you through the initial configuration and verification of your HTTP Ingestion with DB Configuration deployment.
After syncing the project, you'll be prompted to configure the following secrets:
| Secret | Description |
|---|---|
influxdb_admin_token |
Authentication token for InfluxDB. Also used as the Grafana admin password. |
influxdb_admin_password |
Password for InfluxDB UI access. |
http_auth_token |
Authentication token for the HTTP API Source endpoint. |
postgresql_password |
Password for the PostgreSQL database. |
Security Warning: Use strong, unique passwords for each secret. These services may be publicly accessible via the internet.
After syncing and configuring secrets, verify that all services are running:
Core Pipeline (ungrouped):
- HTTP API Source
- HTTP Data Normalization
- HTTP Config Enricher
- InfluxDB2 Sink
- Grafana
- Machine Config UI
Mock Data Source group:
- OPC UA Server
- OPC UA Source
- HTTP Sink
Aux services group:
- InfluxDB2
- postgreSQL
Note: It's normal for services to restart a few times during initial deployment while dependencies start up.
- Click the public URL link on the Grafana deployment
- Log in with:
- Username:
admin - Password: The value you set for
influxdb_admin_token
- Username:
- Click the public URL link on the Machine Config UI deployment
- When embedded in the Quix portal, authentication is automatic via your Quix SDK token
- For standalone access, enter your Quix Personal Access Token (found in Quix Portal → Settings → Personal Access Token)
-
Check mock data generation: The OPC UA Server generates simulated sensor data that flows through OPC UA Source → HTTP Sink → HTTP API Source
-
Verify Kafka topics: In the Quix UI, check that messages are flowing through:
http_data(raw incoming data)normalized_data(aggregated data)config_enriched_data(data with configuration applied)
-
View in Grafana: Navigate to Dashboards and select the printer dashboard to see live data visualization
This is normal during initial deployment. Wait 2-3 minutes for all dependencies to initialize. Services should stabilize after a few restart cycles.
- Verify all services are running (green status)
- Check that data is flowing through Kafka topics
- Ensure the InfluxDB2 Sink is connected and writing data
- Wait a few minutes for data to accumulate
- Verify the service is running
- Check that public access is enabled on the deployment
- Ensure you're using the correct credentials
Verify that the http_auth_token secret matches between:
- HTTP API Source (
HTTP_AUTH_TOKEN) - HTTP Sink (
RECEIVER_AUTH_TOKEN)
- Verify PostgreSQL and InfluxDB2 services are running
- Check that the password secrets are configured correctly
- Services may need to restart after database initialization completes