Dashboard design for agent monitoring in Agentic AI - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key Metrics for Agent Monitoring Dashboard

Which of the following metrics is most important to display on a dashboard monitoring multiple AI agents' health and performance?

A CPU usage, memory consumption, and response latency of each agent

B Number of user clicks on the dashboard interface

C Total number of agents deployed without status details

D Color scheme preferences of the dashboard users

💡 Hint

Think about what helps you understand if agents are working well or need attention.

CPU usage, memory consumption, and response latency directly show agent health and performance, which are critical for monitoring.

💻 Command Output

intermediate

Output of Agent Status Query Command

What is the output of the following command querying agent statuses?

Agentic AI

agentctl status --all --format json

A Error: Unknown command 'agentctl'

B [{"agent_id": "a1", "status": "active"}, {"agent_id": "a2", "status": "inactive"}]

C {"agent_id": "a1", "status": "active"}

D ["a1", "a2", "a3"]

💡 Hint

The command lists all agents with their statuses in JSON format.

The command outputs a JSON array with each agent's ID and current status, showing active and inactive agents.

❓ Configuration

advanced

Configuring Alert Thresholds for Agent Latency

Which configuration snippet correctly sets an alert to trigger if any agent's response latency exceeds 500ms?

A

alerts:
  latency_threshold_ms: 500
  trigger_on: agent_cpu_usage
  action: notify_admin

B

alerts:
  trigger_on: agent_response_latency
  latency_threshold: 'five hundred'
  action: notify_admin

C

alerts:
  latency_threshold_ms: 500
  action: notify_admin

D

alerts:
  latency_threshold_ms: 500
  trigger_on: agent_response_latency
  action: notify_admin

💡 Hint

Look for correct keys and values that match latency and threshold.

Option D correctly specifies the latency threshold in milliseconds, the trigger metric, and the action to notify admin.

❓ Troubleshoot

advanced

Troubleshooting Missing Agent Data on Dashboard

After deploying the dashboard, some agents show no data. What is the most likely cause?

A Dashboard refresh interval is set to 1 second

B Dashboard color scheme is incompatible with agent data format

C Agents are not sending telemetry data due to network issues

D Agent IDs are too long to display on the dashboard

💡 Hint

Think about what stops data from reaching the dashboard.

If agents cannot send telemetry data because of network problems, the dashboard will show missing data for those agents.

🔀 Workflow

expert

Steps to Add a New Agent to the Monitoring Dashboard

What is the correct order of steps to add a new AI agent to the monitoring dashboard?

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 3,1,2,4

💡 Hint

Think about registering first, then configuring data flow, then updating dashboard, then verifying.

The new agent must be registered first, then configured to send data, then the dashboard updated, and finally verification done.

Practice

1. What is the main purpose of a dashboard in agent monitoring?

easy

A. To show agent information in one place for easy tracking

B. To write code for agents

C. To delete agents automatically

D. To store agent data permanently

Solution

1. Step 1: Understand dashboard role

   A dashboard collects and shows important info in one place.

2. Step 2: Identify main benefit

   This helps users track agent status quickly and easily.

3. Final Answer:

   To show agent information in one place for easy tracking -> Option A

4. Quick Check:

   Dashboard purpose = Show info in one place [OK]

Hint: Dashboards gather info visually for quick checks [OK]

Common Mistakes:

• Thinking dashboards write or delete agents
• Confusing storage with display
• Assuming dashboards automate agent tasks

2. Which of the following is the correct way to add a status widget in a dashboard configuration file?

easy

A. "widgets": [{"type": "status", "agentId": "agent_01"}]

B. "widgets": [{type: status, agentId: agent_01}]

C. "widgets": [{"type": status, "agentId": agent_01}]

D. widgets: [{"type": "status", "agentId": "agent_01"}]

Solution

1. Step 1: Check JSON syntax

   Correct JSON requires keys and string values in double quotes.

2. Step 2: Identify correct option

   "widgets": [{"type": "status", "agentId": "agent_01"}] uses proper JSON with quotes around keys and values.

3. Final Answer:

   "widgets": [{"type": "status", "agentId": "agent_01"}] -> Option A

4. Quick Check:

   Proper JSON syntax = "widgets": [{"type": "status", "agentId": "agent_01"}] [OK]

Hint: JSON keys and string values need double quotes [OK]

Common Mistakes:

• Missing quotes around keys or string values
• Using single quotes instead of double quotes
• Omitting commas between items

3. Given this dashboard widget code snippet:

{"type": "chart", "metric": "cpu_usage", "agentId": "agent_02"}

What will this widget display?

medium

A. A status indicator for agent_02

B. A log list for agent_02

C. A chart showing CPU usage for agent_02

D. An error message because of missing fields

Solution

1. Step 1: Identify widget type

   The type is "chart", so it shows a graph or chart.

2. Step 2: Check metric and agent

   Metric is "cpu_usage" for agent "agent_02", so it charts CPU usage for that agent.

3. Final Answer:

   A chart showing CPU usage for agent_02 -> Option C

4. Quick Check:

   Chart type + cpu_usage metric = CPU usage chart [OK]

Hint: Widget type 'chart' means graph display [OK]

Common Mistakes:

• Confusing chart with logs or status
• Assuming missing fields cause errors here
• Ignoring the metric field

4. You added a log widget but it shows no logs. Which fix is most likely correct?

medium

A. Remove the widget and add a status widget instead

B. Check if the agentId in the widget matches the actual agent ID

C. Restart the dashboard server without changing config

D. Change the widget type to "chart" without updating other fields

Solution

1. Step 1: Identify common cause of empty logs

   Logs show empty if the agentId is wrong or missing.

2. Step 2: Fix agentId in widget config

   Correcting agentId to match the real agent fixes log display.

3. Final Answer:

   Check if the agentId in the widget matches the actual agent ID -> Option B

4. Quick Check:

   Correct agentId fixes empty logs [OK]

Hint: Verify agentId matches actual agent for logs [OK]

Common Mistakes:

• Restarting server without config fix
• Changing widget type without reason
• Removing widget instead of fixing config

5. You want a dashboard that shows agent status, CPU charts, and recent logs all in one view. Which design approach is best?

hard

A. Create separate dashboards for each info type

B. Use a single widget that tries to show all info together

C. Only show status widgets to keep dashboard simple

D. Use multiple widgets: one status widget, one chart widget, and one log widget

Solution

1. Step 1: Understand dashboard modular design

   Dashboards use multiple widgets to show different info types clearly.

2. Step 2: Choose best approach for combined info

   Using separate widgets for status, charts, and logs keeps info organized and easy to read.

3. Final Answer:

   Use multiple widgets: one status widget, one chart widget, and one log widget -> Option D

4. Quick Check:

   Multiple widgets for different info = best design [OK]

Hint: Combine widgets for clear, organized dashboard [OK]

Common Mistakes:

• Trying to cram all info in one widget
• Splitting info into separate dashboards unnecessarily
• Showing only status and ignoring other data