Sven laptop
635a130f0b
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
### Summary of Changes
1. Documentation Consolidation:
• Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
• Updated document links in README.md.
2. AI Agent Project Map:
• Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
schemas, environment variables, and developer workflows.
• Added PROJECT_MAP.md to .gitignore.
3. Monitoring UI & Infrastructure Integration:
• Added monitoring_ui service to docker-compose.yml (port 5175).
• Configured Gitea workflow docker-build.yml for monitoring_ui builds.
• Added CORS middleware headers in index.js.
• Added nginx.conf copy step in Dockerfile.
──────
### Recommended Commit Message
docs: consolidate project documentation into monitoring_ui and add agent project map
- Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
- Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
- Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
- Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
- Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
- Configure CORS handling in employee_api for monitoring dashboard access
──────
### Alternative Short Commit Message
refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
74 lines
4.9 KiB
Markdown
74 lines
4.9 KiB
Markdown
<!-- azure-cor-disclaimer -->
|
||
> **Important:** This skill provides guidance and recommended instructions to assist the AI system. Outputs are not guaranteed to be complete, correct, secure, or applicable to every scenario. Results should be reviewed and validated by a human before being applied. The AI model may choose not to follow all instructions exactly, and additional verification may be required.
|
||
|
||
# App Onboard Prepare — Pricing Guide
|
||
|
||
> ⛔ **SELF-CHECK:** If `costEstimate.breakdown[]` has ANY `monthlyUsd > 0`, at least one `pricing_get` or `az rest` pricing API call MUST appear in this session. Estimating from memory or training data is NEVER acceptable — reference values in this file may be outdated. If API fails after 2 attempts, use the reference value WITH disclaimer: `"⚠️ Estimated from reference — live API unavailable."`
|
||
|
||
## No Free-Tier Shortcut — Compute Always Has Cost
|
||
|
||
> ⛔ **There is no $0 shortcut.** Compute has a floor (App Service **B1**, Static Web Apps **Standard**, Functions **Flex Consumption**) — F1/D1/Free/Consumption are never selected (see [sku-matrix.md](sku-matrix.md)). So any app with a compute component has a non-zero monthly cost and MUST get a live pricing call. Do NOT write a $0 estimate for a compute app.
|
||
|
||
Some services can still fall within free **grant** limits (they are metered, not a fixed free SKU) — note the grant in the estimate but still price the paid meters:
|
||
|
||
| Service | Free grant (still price paid usage above it) |
|
||
|---------|-----------------------------------------------|
|
||
| Functions (Flex Consumption) | First 250K executions + 100K GB-s/month |
|
||
| Cosmos DB | Free-tier account: 1000 RU/s + 25 GB (one per subscription) |
|
||
| Container Apps | First 180K vCPU-s + 360K GiB-s + 2M requests/month |
|
||
| Log Analytics | First 5 GB/month ingestion |
|
||
|
||
---
|
||
|
||
## App Service Quick Reference
|
||
|
||
| SKU | `skuName` | Monthly |
|
||
|-----|-----------|---------|
|
||
| B1 Linux | `B1` | ~$13.14 |
|
||
|
||
> ⛔ **Case-sensitive:** use `B1` not `b1`. Use `skuName` (not `armSkuName`) for Basic/Standard.
|
||
|
||
---
|
||
|
||
## How to Use
|
||
|
||
1. Pick SKU from [sku-matrix.md](sku-matrix.md) based on budget intent.
|
||
2. Find service section in [pricing-guide-services.md](pricing-guide-services.md) for filter strings and formulas.
|
||
3. Call the pricing router — tool `mcp_azure_mcp_pricing` (VS Code) / `azure-pricing` (CLI) — with `intent`, `command: "pricing_get"`, and a `parameters` object (NOT `--flags`). Parallel OK. ⛔ At least one filter inside `parameters`: `sku`, `service`, `region`, `service-family`, or `filter`. ⛔ **`sku` matches `armSkuName`, not `skuName`** — use it ONLY when `armSkuName` is populated (App Service, MySQL/PostgreSQL, Redis). Empty-`armSkuName` services (ACR, Storage, Cosmos) return `[]` or 400 for `sku`/`service` — use a raw `filter` on `serviceName` + `meterName` instead.
|
||
4. Apply the monthly multiplier from each meter's `unitOfMeasure` (see § Monthly Multiplier) — NOT a per-service constant.
|
||
5. Cross-check returned `retailPrice` against planned SKU.
|
||
|
||
## Monthly Multiplier — by Meter Unit
|
||
|
||
⛔ **Read `unitOfMeasure` per price record — NEVER blanket `× 730`** (one service mixes units, e.g. ACR returns `1/Day` + `1 Second` + `1 GB/Month`):
|
||
|
||
| `unitOfMeasure` | Monthly formula |
|
||
|-----------------|-----------------|
|
||
| `1 Hour` / `1/Hour` | `retailPrice × 730` |
|
||
| `1/Day` / `1 Day` | `retailPrice × 30` |
|
||
| `1 GB/Month` | `retailPrice × estimatedGB` (already monthly) |
|
||
| `1 Second` / `1 GiB Second` | `retailPrice × activeUnitsPerMonth` (usage-based) |
|
||
| `10K` / `1M` operations | `retailPrice × estimatedOps ÷ unitSize` |
|
||
|
||
## Usage-Based Services
|
||
|
||
When AI/OpenAI/LLM components detected: add `"💸 Usage-based — excluded from total"` to `costEstimate.breakdown[]` and `"⚠️🤖 AI inference costs excluded"` to `assumptions[]`. Surface at EVERY approval gate.
|
||
|
||
## Service Pricing Reference
|
||
|
||
See [pricing-guide-services.md](pricing-guide-services.md) for per-service filter strings, meter names, and monthly formulas.
|
||
|
||
**Key rules:**
|
||
- `armSkuName` is empty for most PaaS — filter by `meterName` or `productName`
|
||
- Monthly multiplier: read `unitOfMeasure` (§ Monthly Multiplier) — never assume ×730
|
||
- Functions Consumption / Static Web Apps: not in API
|
||
- Default `isPrimaryMeterRegion eq true` + `priceType eq 'Consumption'` — but check the service section in [pricing-guide-services.md](pricing-guide-services.md) first; some drop `isPrimaryMeterRegion` (Service Bus, Cosmos 100 RU/s, Redis Basic).
|
||
- Service names are case-sensitive
|
||
|
||
## Troubleshooting
|
||
|
||
When `pricing_get` returns empty: (1) Check `armSkuName` populated/case-sensitive? (2) HTTP fallback: `https://prices.azure.com/api/retail/prices?$filter={filter}`. (3) After 2 failures, use [pricing-guide-services.md](pricing-guide-services.md) with disclaimer. (4) Log to `costEstimate.apiFailures[]`.
|
||
|
||
> ⛔ **Never claim user has free credits remaining.** Use: "Check balance at portal."
|
||
|