Skip to content
#

dashboard

Here are 7,032 public repositories matching this topic...

netdata
HolgerHees
HolgerHees commented May 17, 2019

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

help wanted feature request area/health good first issue
grafana
alexweav
alexweav commented Jun 13, 2022

What happened:

When creating a Slack contact point, I am unable to save unless the Webhook URL field is populated. However, right above the field, it says that the field is optional. This doesn't make sense.

Also, if you are trying to make a token-based (non-webhook) Slack bot, this bug makes it impossible. Token-based bots must have a blank webhook URL, or it'll try to send it as a we

type/bug area/alerting area/alerting/unified good first issue
strapi
sujaydeymountblue
sujaydeymountblue commented May 31, 2020

Describe the bug
At the time of registration, email has not been validated correctly http://localhost:1337/admin/auth/register

Expected behavior
An email should be valid in all aspect like

  • should check valid domain, well-formed and valid mailbox

Screenshots
invalid email1:
s1

issue: enhancement severity: low good first issue
directus
chatwoot
vishnu-narayanan
vishnu-narayanan commented Mar 30, 2022

Is your enhancement request related to a problem? Please describe.

Clear visual indication when an integration/application is connected/active.

Slack is fully connected and active at this stage. It would be nice to have a visual indicator on this page to know slack is connected without clicking on configure and navigating to another page.

![image](https://user-images.githubuserconte

Good first issue frontend need-discussion
emmanuelle
emmanuelle commented Nov 28, 2019

Most items coming from questions on the community forum

documentation good first issue
bandwhich
llchan
llchan commented Mar 31, 2020

It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.

  • For the "Utilization by process name" window, we could group by pid rather than process name so that it's easier to find specific heavy network resource consumers.
  • For the "Utilization by connection" window, including the pid + cmdlin
help wanted good first issue

Improve this page

Add a description, image, and links to the dashboard topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the dashboard topic, visit your repo's landing page and select "manage topics."

Learn more