dispatcher client stats breaks admin dashboard
See original GitHub issueI’m looking at the admin dashboard for the gob app running in Kubernetes. When I try to view the “http” router, I see:
Here’s the metrics payload that produced the error:
I think the issue is:
{
"rt": {
"http": {
"client": {
"$/inet/127.1/8282": {
...
},
"dispatcher": {
"serial": {
"queue_size": {
"gauge": 0
}
}
}
}
}
}
}
The “dispatcher” key in the “client” map doesn’t match the TRANSFORMER_RE that we use to parse client ids in the js code. Maybe we should just skip all client ids that don’t match the regex? Or maybe those dispatcher stats aren’t scoped properly?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Configuring Dispatcher | Adobe Experience Manager
The statfile has no content. When content is updated, Dispatcher updates the timestamp. The default statfile is named .stat and is stored in...
Read more >Explore the Dispatcher Console Unit - Trailhead - Salesforce
Use the dispatcher console to manage appointments, schedules, service resources, and maps.
Read more >Latest version breaks Admin Dashboard - WordPress.org
Latest version breaks Admin Dashboard. Resolved mborin ... After upgrading to the latest version I can not expand menu links and Jetpack stats...
Read more >Dispatcher Activities - Oracle Help Center
Dashboard, Access the reports Dashboard to generate reports. ; Daily, Access the Daily view of a resource, a bucket, or an organization unit....
Read more >React Admin Dashboard Template Design - YouTube
React admin dashboard from scratch for beginners. React Admin Panel UI.Get Hostinger Discount: http://hostinger.com/lamadev Coupon Code: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I believe this is caused by https://github.com/twitter/finagle/pull/629
Fixed!