Skip to content

Dummy App

Deploy test applications to verify that Container Insights is collecting logs correctly.

Overview

The application deployment is unchanged. Container Insights automatically collects stdout/stderr from all pods — no sidecar, annotation, or log agent configuration is needed on the application side.

Deploy the Dummy Ness App

This is a simple pod with a shell script that echoes a message every 5 seconds: 
kubectl apply -f dummy-app/dummy-ness-app.yaml

Deploy the Ness App (Java)

This is a sample Java implementation that outputs logs in ness format: 
kubectl apply -f ness-app.yaml

Verify Logs Are Being Collected

After deploying, wait 5–10 minutes for logs to appear in Log Analytics, then run: 
ContainerLogV2
| where TimeGenerated > ago(15m)
| where PodName startswith "dummy-ness" or PodName startswith "ness-app"
| project TimeGenerated, PodName, ContainerName, LogMessage, LogSource
| order by TimeGenerated desc
| take 20

Check Pod Status

# Verify pods are running
kubectl get pods -n default -l app=dummy-ness-app
kubectl get pods -n default -l app=ness-app

# View live logs from the pod directly
kubectl logs -l app=dummy-ness-app --tail=10
kubectl logs -l app=ness-app --tail=10

Notes

  • No changes to Dockerfiles, entrypoints, or application code are needed
  • Any application that writes to stdout or stderr is automatically collected
  • Logs are enriched with pod name, namespace, node, container name, labels, and annotations by Container Insights
  • If pods are running but no logs appear in ContainerLogV2, verify that the namespace is not in the exclude_namespaces list in the ConfigMap (see Implementation → Step 4)