Vendor Stack Tags

Vendor stack tags tell Merlonix which third-party services your clients depend on. When a tagged vendor has an incident, Merlonix matches the incident against your tags and adds it to your alerts, your status page, and your monthly report.

Without stack tags, you receive SSL and DNS monitoring only. With stack tags, you also see: "Stripe's checkout service is degraded" or "Cloudflare's CDN has an incident" — surfaced in the same dashboard and report as your infrastructure monitoring.

Why stack tags exist at the account level

Stack tags are set on your tenant (account), not on individual assets. This reflects how agencies actually work: you have a portfolio of clients, most of whom share similar infrastructure — they are all on Shopify, or all using Stripe for payments, or all running on Cloudflare.

When Stripe has a checkout incident, it potentially affects every e-commerce client in your portfolio simultaneously. Setting payments.checkout at the account level means you get one alert covering your entire portfolio, not one alert per asset.

If different clients use radically different stacks, consider whether those clients are better served as separate tenants.

Configuring stack tags

In the dashboard

Navigate to Settings → Account
Scroll to Vendor stack
Select tags from the supported catalog (grouped by vendor)
Click Save

Tags take effect immediately. The next vendor incident check will match against your updated tags.

Via API

PATCH /v1/customers/me
Authorization: Bearer <token>
Content-Type: application/json

{
  "stack_tags": [
    "payments.checkout",
    "payments.webhooks",
    "network.cdn",
    "network.dns",
    "admin.storefront",
    "admin.checkout"
  ]
}

The stack_tags field is the complete replacement — not append-only. Send the full array of tags you want active. See API Integration Reference for authentication details.

Supported vendors and tags

Merlonix monitors 11 vendors. Each vendor has a fixed catalog of component tags. Only tags in this catalog are accepted.

Stripe

Tag	Component
`payments.checkout`	Checkout sessions and hosted checkout pages
`payments.webhooks`	Webhook delivery
`payments.dashboard`	Stripe Dashboard
`payments.connect`	Connect accounts and transfers
`payments.api`	Core Stripe API
`billing.invoicing`	Invoice creation and delivery
`billing.subscriptions`	Subscription billing engine
`radar.fraud`	Fraud detection and rules

Cloudflare

Tag	Component
`network.dns`	Cloudflare DNS resolution
`network.cdn`	CDN and caching
`network.workers`	Workers execution
`network.pages`	Pages hosting
`network.r2`	R2 object storage
`network.tunnel`	Cloudflare Tunnel
`security.waf`	Web Application Firewall
`security.ddos`	DDoS protection
`security.turnstile`	Turnstile CAPTCHA

Amazon Web Services (AWS)

Tag	Component
`compute.ec2`	EC2 virtual machines
`compute.lambda`	Lambda functions
`compute.ecs`	ECS container service
`storage.s3`	S3 object storage
`storage.ebs`	EBS block storage
`database.rds`	RDS managed databases
`database.dynamodb`	DynamoDB
`network.cloudfront`	CloudFront CDN
`network.route53`	Route 53 DNS
`network.vpc`	VPC networking
`auth.iam`	IAM identity and access
`messaging.sqs`	SQS message queues
`messaging.sns`	SNS notifications

Shopify

Tag	Component
`admin.storefront`	Storefront rendering and Liquid
`admin.checkout`	Checkout flow
`admin.api`	Shopify Admin API
`admin.webhooks`	Shopify webhook delivery
`payments`	Shopify Payments processing
`pos`	Point of Sale

GitHub

Tag	Component
`git.operations`	Git push, pull, clone
`api.rest`	GitHub REST API
`api.graphql`	GitHub GraphQL API
`actions.workflows`	GitHub Actions CI/CD
`packages.registry`	GitHub Packages
`pages`	GitHub Pages hosting
`codespaces`	GitHub Codespaces

Vercel

Tag	Component
`hosting.builds`	Build pipeline
`hosting.edge_runtime`	Edge Runtime execution
`hosting.serverless`	Serverless Function execution
`hosting.dns`	Vercel DNS
`hosting.domains`	Custom domain routing
`analytics`	Vercel Analytics

Slack

Tag	Component
`messaging.api`	Slack Web API
`messaging.webhooks`	Incoming Webhooks
`apps.events`	App event subscriptions
`calls`	Huddles and calls
`files.upload`	File uploads

Google Cloud

Tag	Component
`compute.compute_engine`	Compute Engine VMs
`compute.cloud_run`	Cloud Run
`compute.cloud_functions`	Cloud Functions
`storage.cloud_storage`	Cloud Storage
`database.cloud_sql`	Cloud SQL
`database.firestore`	Firestore
`ai.vertex`	Vertex AI
`ai.gemini_api`	Gemini API
`network.load_balancing`	Load Balancing
`auth.iam`	IAM and identity

Microsoft Azure

Tag	Component
`compute.vms`	Virtual Machines
`compute.functions`	Azure Functions
`compute.app_service`	App Service
`storage.blob`	Blob Storage
`database.sql`	Azure SQL
`database.cosmos`	Cosmos DB
`ai.openai`	Azure OpenAI Service
`auth.entra_id`	Entra ID (Azure AD)

OpenAI

Tag	Component
`api.chat`	Chat Completions API
`api.embeddings`	Embeddings API
`api.images`	Image generation API
`api.audio`	Audio transcription and TTS
`api.assistants`	Assistants API
`api.batch`	Batch API

Anthropic

Tag	Component
`api.messages`	Messages API
`api.batch`	Message Batches API
`api.files`	Files API
`console`	Anthropic Console

What happens when a vendor has an incident

When Merlonix detects an incident on a tagged vendor:

The incident is matched against your stack_tags
If any of your tags overlap the affected components, an alert is created in your account
The alert appears in your dashboard under Alerts with type vendor_incident
If you have alert channels configured, notifications are sent to channels with warning or critical severity filters matching the incident severity
The incident is logged in your monthly report under Vendor incidents
Your status page (if enabled) shows the vendor incident in the incident timeline

Vendor incidents typically resolve within hours. When the incident resolves, Merlonix marks the alert as resolved and logs the resolution time.

Typical configuration by agency type

E-commerce agencies (Shopify + Stripe):

["admin.storefront", "admin.checkout", "admin.api", "payments.checkout", "payments.webhooks", "payments.api"]

Web agencies (Cloudflare CDN + GitHub):

["network.cdn", "network.dns", "git.operations", "actions.workflows"]

SaaS-focused agencies (AWS + Stripe):

["compute.ec2", "compute.lambda", "storage.s3", "database.rds", "payments.api", "payments.webhooks", "billing.subscriptions"]

Full-stack digital agencies:

["network.cdn", "network.dns", "admin.storefront", "admin.checkout", "payments.checkout", "payments.webhooks", "git.operations", "actions.workflows"]

Start with the services you know clients depend on for revenue — checkout flows, payment processing, and CDN are the highest-impact. Add infrastructure tags (compute, storage, database) only if you manage those layers directly.

Next: read Monthly Reports to see how vendor incidents appear in client-ready report output, or Client Status Pages to understand how vendor status is displayed on the public status URL.