General

Profile

Patrick Seidensal

  • Registered on: 06/14/2017
  • Last connection: 10/17/2019

Issues

Projects

  • mgr (Developer, Reporter, 03/13/2018)

Activity

10/17/2019

09:17 AM mgr Bug #41911 (In Progress): mgr/dashboard: Smart data tab stays empty when backend returns neither ...
08:09 AM mgr Bug #41747 (Verified): mgr/dashboard: custom pool application tags cannot be removed during edit

10/14/2019

04:12 PM mgr Cleanup #42310 (New): mgr/dashboard: silences: matchers is displayed as JSON object
On the `Silences` page of the dashboard, when selecting a silence, the details of that silence are displayed below in...
04:06 PM mgr Cleanup #42309 (New): mgr/dashboard: editing silence: confusion about editing and recreating sile...
On the table of the `Silences` page:
When an expired silence is selected, the `Edit` action in the menu is deactiv...
03:59 PM mgr Bug #42308 (New): mgr/dashboard: editing silence: editing matcher: hint is only shown for non-reg...
When editing a matcher on the `Edit Silence` form of the `Silences` page, a message is shown:
Your matcher seems t...
03:55 PM mgr Cleanup #42307 (New): mgr/dashboard: editing silence: symbols for matchers are obscure
The chosen icons for the matchers than can be defined to create a silence are rather obscure. The pilcrow (ΒΆ) symbol ...
03:44 PM mgr Cleanup #42306 (New): mgr/dashboard: editing silence: page width too small
With a page width of ~1500px the form for editing a silence is still rather small and the values of matcher cannot be...
03:39 PM mgr Cleanup #42305 (New): mgr/dashboard: editing silence: order of fields seems unintuitive
The creator and comment of a new silence is the first and second field, although they do not seem to be such importan...
03:35 PM mgr Cleanup #42304 (New): mgr/dashboard: alerts and silences pages improvements
When looking at the implementation of the silences and alerts of the dashboard, I came across some things that might ...

10/10/2019

11:30 AM mgr Feature #42253: mgr/dashboard: Define and document valid frontend tests
Nice pyramid:
> As a good first guess, Google often suggests a 70/20/10 split: 70% unit tests, 20% integration tes...

Also available in: Atom