[Dashboard Request] Golang Runtime Metrics Dashboard

[makeavish]

📝 Dashboard Request Template

1. Dashboard Name

Golang Runtime Metrics Dashboard

---

2. Suggested Dashboard Sections and Panels - Tweak based on relevancy and available metrics

Section: Memory Metrics

• Panel: Heap Allocation - Displays the current number of bytes allocated on the heap.
• Panel: Heap Idle - Shows memory allocated by the OS but not actively used by the Go runtime.
• Panel: Heap In Use - Shows the memory currently in use for heap objects.
• Panel: Heap Objects - Displays the number of allocated heap objects.
• Panel: Heap Released - Memory released back to the OS.
• Panel: Heap Sys - Total bytes obtained from the system for the heap.
• Panel: GC Pause Duration - Duration of garbage collection pauses.
• Panel: GC Count - Displays the number of completed garbage collection cycles.
• Panel: GC Forced - Shows the number of times garbage collection has been forced.

Section: Goroutines Metrics

• Panel: Active Goroutines - Displays the current number of active goroutines.
• Panel: Total Goroutines Created - Shows the total number of goroutines created since the program started.

Section: GC (Garbage Collection) Metrics

• Panel: CPU Fraction - Displays the fraction of total CPU time spent in garbage collection.
• Panel: GC Sys - Bytes used by garbage collection metadata.

Section: CPU Metrics

• Panel: Goroutine Execution Time - Total time in nanoseconds spent in goroutine execution.
• Panel: GC Time - Displays time spent in garbage collection in nanoseconds.
• Panel: System Time - Displays time spent by the Go runtime in system-related tasks.

Section: Thread Metrics

• Panel: OS Threads - Displays the number of OS threads created by the Go runtime.

Section: Stack Metrics

• Panel: Stack In Use - Memory currently used for goroutine stacks.
• Panel: Stack Sys - Displays the total bytes obtained from the system for stacks.

Section: Mutex and Semaphores Metrics

• Panel: Mutex Wait Time - Time spent waiting on mutex locks.
• Panel: Mutex Lock Count - Number of mutex lock operations.

---

3. Expected Variables

• deployment.environment
• service.name

---

4. Additional Comments or Requirements

No additional requirements for now.

---

📋 Notes

Please review the CONTRIBUTING.md for guidelines on dashboard structure, naming conventions, and how to submit a pull request.

Instrument with otel golang runtime

Refer this dashboard for inspiration: https://grafana.com/grafana/dashboards/14061-go-runtime-metrics/

---

[makeavish]

/bounty 150

[algora-pbc]

💎 $150 bounty • SigNoz

Steps to solve:

1. Start working: Comment /attempt #6007 with your implementation plan
2. Submit work: Create a pull request including /claim #6007 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to SigNoz/signoz!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🔴 @mobley-trent	Sep 19, 2024, 6:35:59 AM	WIP
🟢 @Rishabh3321	Sep 24, 2024, 9:27:02 PM	#83
🟢 @karanveersingh5623	Oct 28, 2024, 1:39:43 PM	WIP
🟢 @nishchay-veer	Oct 28, 2024, 3:40:14 PM	#99

[mobley-trent]

/attempt #6007

Algora profile	Completed bounties	Tech	Active attempts	Options
@mobley-trent	10 bounties from 5 projects	Python, Rust, Jupyter Notebook		Cancel attempt

[Rishabh3321]

/attempt #6007

Options

• Cancel my attempt

[algora-pbc]

💡 @Rishabh3321 submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[karanveersingh5623]

/attempt #6007

Options

• Cancel my attempt

[nishchay-veer]

/attempt #6007

Options

• Cancel my attempt

[algora-pbc]

💡 @nishchay-veer submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[ExitoLab]

/attempt #6007