only-en qualiweeks pick-24 added captions

Author: bili123

src/common/en/dashboards.asciidoc

@@ -62,6 +62,7 @@ On the {CMK} start page you will see the [.guihint]#Main dashboard,# which can b
 ifdef::onprem[]
 {RE} and commercial editions each come with their own individual standard dashboards, so here is a look at the commercial editions variant first:
 
+.The standard dashboard of a commercial edition with the host overview
 image::dashboard_main_numbered.png[alt="The standard dashboard of the commercial editions with numbers for the detailed description."]
 
 [cols="7,~,<.>~", options="header"]
@@ -85,12 +86,14 @@ If you move the mouse pointer over the graphs or the host symbols in the [.guihi
 
 On {CRE}, however, the main dashboard on the start page is the [.guihint]#Problem Dashboard#, which can also be called up in the commercial editions via icon:icon_dashboard_problems[alt="Icon of the Problem dashboard."] and which, quite conventionally, shows unresolved problems and current events in the form of a list:
 
+.The dashboard of the Open Source version showing service issues
 image::dashboard_main_numbered_raw.png[alt="The {RE} standard dashboard with numbers for the detailed description."]
 endif::[]
 
 ifdef::saas[]
 The main dashboard shows unresolved problems and current events in the form of a list:
 
+.The standard dashboard of {CE}
 image::dashboard_main_numbered_saas.png[alt="The standard dashboard with numbers for the detailed description."]
 endif::[]
 
@@ -180,18 +183,21 @@ all with automatic height, the side ones also with automatic width
 -- the dashlets at the top and bottom get the setting [.guihint]#max width#.
 By default, the anchor is at the top left, but here the right dashlet gets the anchor at the top right and the bottom one at the bottom left.
 
+.Manually positioned and scaled matrix dashlet
 image::dashboard_layout_example_1.png[alt="A host matrix dashlet in the dashboard center."]
 
 If you now move the host matrix dashlet further to the left and down, for example, the host overview dashlets on the left, right and bottom change
 -- because they automatically grow from their anchors towards the central host matrix dashlet.
 
 The top dashlet, on the other hand, remains as it is -- after all, it cannot grow downwards because the two side dashlets are anchored at the top.
 
+.Dashlets with [.guihint]#auto width/height# adjust to fit automatically
 image::dashboard_layout_example_2.png[alt="The host matrix dashlet, moved to the bottom left."]
 
 If you now switch the lower dashlet from [.guihint]#max width# to [.guihint]#auto width# it no longer extends over the entire width
 -- because the automatic height of the right dashlet is rendered before the automatic width of the lower dashlet.
 
+.A question of hierarchy: The automatic height of the right-hand dashlets is set before the automatic widths of the bottom dashlets are set.
 image::dashboard_layout_example_3.png[alt="The bottom dashlet with shortened width."]
 
 If dashlets with automatic dimensions are competing for the same space, you can use the maximum setting to determine the winner, so to speak
@@ -206,12 +212,14 @@ The whole dynamic layout principle is easier to understand if you create such a
 You will see the dashboard configuration automatically when you create a new dashboard,
 later you can access it via the icons in the dashboard list ([.guihint]#Customize > Visualization > Dashboards#) or the [.guihint]#Dashboard > Properties# menu item in an open dashboard.
 
+.Layout and configuration can be edited separately
 image::dashboard_config_dashboard.png[alt="The 'Dashboard' menu with the 'Properties' entry selected.",width=60%]
 
 The properties of the dashboard itself are trivial;
 only metadata such as name, menu item or visibility are defined here, as well as context filters if required.
 Context filters simply restrict dashboards and dashlets to certain hosts and/or services.
 
+.Where and for whom is the dashboard visible?
 image::dashboard_config_example_dashboard.png[alt="General properties of the dashboard."]
 
 
@@ -221,6 +229,7 @@ image::dashboard_config_example_dashboard.png[alt="General properties of the das
 You will see the configuration of individual dashlets automatically when you add them to a dashboard;
 later you can call them up directly via a dashlet's 'cogwheel' icon in the layout mode.
 
+.Opening the Dashlet configuration menu
 image::dashboard_config_dashlet.png[alt="The icon for calling up the properties of a dashlet.",width=60%]
 
 The configuration of most dashlets is quite simple, as the dashlet with the host matrix from the screenshots above shows.
@@ -229,6 +238,7 @@ For all dashlets that refer to several or individual hosts and services, you wil
 And finally, some dashlets offer options for the precise design of the visualization, for example via limit values.
 As an example, here is the [.guihint]#Properties# box of the [.guihint]#Gauge# dashlet:
 
+.The [.guihint]#Gauge# dashlets' features can be used to visualize a wide variety of data.
 image::dashboard_config_example_dashlet.png[alt="Properties of the 'Gauge' dashlet."]
 
 
@@ -240,6 +250,7 @@ Even away from the dashboard and dashlet configuration, there are important sett
 Under [.guihint]#Setup > Users > Roles & permissions > Edit role user# you can simply filter for `dashboard` to list all options.
 Here for a xref:wato_user#roles[role] you can specify in detail which standard dashboards its assigned users can see and what exactly they are allowed to do with other dashboards.
 
+.Dashboards may contain sensitive information -- not every user role needs all rights here
 image::dashboard_config_permissions.png[alt="User role with the permissions for dashboards."]
 endif::[]
 
@@ -261,6 +272,7 @@ and the [.guihint]#Scheduled downtimes# view lists xref:glossar#scheduled_downti
 
 And this is what the finished dashboard will look like:
 
+.A dashboard with four dashlets -- for CPU usage, file system, notification statistics, and scheduled maintenance times
 image::dashboard_example_view.png[alt="The example dashboard created below."]
 
 
@@ -272,6 +284,7 @@ image::dashboard_example_view.png[alt="The example dashboard created below."]
 First create a dashboard via [.guihint]#Customize > Visualization > Dashboards > Add dashboard#.
 This will immediately take you to the first basic setting:
 
+.This first filter determines which data will be available to the dashboard.
 image::dashboard_example_1.png[alt="Selection of object types for the dashboard."]
 
 With [.guihint]#Select specific object type# you can restrict the dashboard to certain hosts, services and even individual objects such as Docker images or fans.
@@ -280,6 +293,7 @@ You can still filter this later.
 
 Then use [.guihint]#Continue# to access the properties of the dashboard to be created.
 
+.This second filter option determines which data is displayed by default in the dashboard
 image::dashboard_example_2.png[alt="General properties of the dashboard with the necessary input for ID and title."]
 
 All that is required here is a name and title for the dashboard in the [.guihint]#General properties# box, here we have used `my_dashboard` and `My Dashboard`.
@@ -310,23 +324,27 @@ Since the root file system of the host `myhost` is to be visualized here, `My Ho
 As with many input fields in {CMK}, this can be done more conveniently via macros: `$HOST_NAME$: $SERVICE_DESCRIPTION$`
 Which macros you can use may be found in the help texts, which you can display with [.guihint]#Help > Show inline help#.
 
+.An interesting line: [.guihint]#Show information of single ... hosts, service# provides information about available data
 image::dashboard_example_3.png[alt="General settings of the 'Performance graph' dashlet."]
 
 In the box for the context filters, enter the host name and the desired file system.
 In both input fields you can simply enter the first letter and then scroll through the possible entries with the down arrow key.
 
+.A third filtering option: Here, filtering is performed by host and/or service -- and it is determined which metric filters will be available in the next step.
 image::dashboard_example_4.png[alt="Context filter of the 'Performance graph' dashlet."]
 
 In the third box, [.guihint]#Properties#, the two filters are automatically adopted for the setting [.guihint]#Graph#.
 You only have to select the desired graph, here [.guihint]#Size and used space#.
 You can leave the other display options unaltered.
 
+.The fourth filter option: A specific metric is selected from the host services that have already been filtered
 image::dashboard_example_5.png[alt="Properties of the 'Performance graph' dashlet."]
 
 If you now save the dashlet, you will arrive in layout mode.
 Since the dashlet should run across the entire width, click [.guihint]#manual width#, to switch the manual width to [.guihint]#auto width#.
 The anchor can remain in its default position at the top left.
 
+.Manual, automatic, maximum extension -- trying these out helps you to understand their functions!
 image::dashboard_example_6.png[alt="The 'Performance graph' dashlet in the layout mode of the dashboard."]
 
 
@@ -346,13 +364,15 @@ However, this time you have to define another setting, namely the maximum of the
 Here select [.guihint]#Floating point number# and set the maximum to `10`.
 Without this you will get an error message.
 
+.This dashlet can also indicate service status -- useful for critical elements.
 image::dashboard_example_7.png[alt="Properties of the 'Gauge' dashlet."]
 
 After saving, you return to layout mode and can place the dashlet below the performance graph (which is initially overlaid by the new dashlet!).
 Manual width and height can be used here.
 You can determine the desired size by dragging the dashlet edges with the mouse.
 At this point you could also set the graph dashlet to automatic height and then simply let the height be determined by the placement of the new gauge dashlet.
 
+.Dashlets can be cloned directly in the layout mode -- handy for creating an initial overall layout
 image::dashboard_example_8.png[alt="The 'Gauge' dashlet in the layout mode of the dashboard."]
 
 
@@ -368,15 +388,18 @@ Data from several hosts and services should now end up in this dashlet -- hence
 To get all alerts from all hosts that start with `my`, set the host name filter to `^my`.
 With this dashlet, it is often a good idea to dispense with filters completely in order to evaluate all hosts.
 
+.Regular expressions enable the creation of graphs with precisely filtered metrics from multiple hosts
 image::dashboard_example_9a.png[alt="Context filter of the 'Alert timeline' dashlet."]
 
 For our example dashlet, the display [.guihint]#Bar chart# is kept, the time range is set to [.guihint]#The last 35 days#, and the resolution is set to whole days.
 
+.Information such as a time period is also useful for descriptive dashlet titles
 image::dashboard_example_9b.png[alt="Properties of the 'Alert timeline' dashlet."]
 
 After saving, place the dashlet back on the dashboard.
 Again an automatic width with manual height is a good way to fill the row with the [.guihint]#Gauge# dashlet.
 
+.In this setup, [.guihint]#max width# would have the same effect in the Alert Dashlet
 image::dashboard_example_9c.png[alt="The 'Alert timeline' dashlet in the layout mode of the dashboard."]
 
 
@@ -388,10 +411,12 @@ This works via [.guihint]#Add > Link to existing view#, but also via the views t
 To add the xref:glossar#scheduled_downtime[scheduled downtimes] view, for example, call it up via [.guihint]#Monitor > Overview > Scheduled downtimes#.
 Then add this view to your dashboard via [.guihint]#Export > Add to dashboard#
 
+.All table displays in {CMK} can be exported to dashboards
 image::dashboard_example_10.png[alt="The 'Export' menu of the 'Scheduled downtimes' view.",width=55%]
 
 Select your dashboard.
 
+.Dashboard selection by name/ID -- another incentive to use descriptive names
 image::dashboard_example_10a.png[alt="Selection of the dashboard for the view."]
 
 Place the dashlet as the last row.
@@ -402,6 +427,7 @@ If you now call up the icon:icon_dashlet_edit[alt="Icon for the properties."] da
 
 With that, your example dashboard is ready, shown here again completely in layout mode:
 
+.The exported [guihint]#Scheduled downtimes# view fills the rest of the dashboard
 image::dashboard_example_11.png[alt="The complete example dashboard in layout mode."]
 
 
@@ -425,6 +451,7 @@ The [.guihint]#Required context filters# can also be found in the dashboard prop
 They are only set as required filters.
 A dashboard with such defaults appears in the dashboard view without information on hosts and services, but with the filter function open and the reference to this [.guihint]#Mandatory context#, which the user must set at runtime, so to speak.
 
+.These filters must be filled in by viewers in the monitoring system itself
 image::dashboard_example_mandatory.png[alt="Filter bar with mandatory context when opening the dashboard.",width=60%]
 
 
@@ -562,11 +589,13 @@ For your own dashboards, you can also create links to other dashboards by linkin
 Let's take a concrete example:
 Here you see a dashboard that shows information on the CPU, RAM and file systems of all hosts that start with `my`.
 
+.Top-down dashboards are implemented via links, here in the graph’s title
 image::dashboard_topdown1.png[alt="Example dashboard of all hosts starting with 'my'."]
 
 In this example the title of the CPU graph links to another dashboard that visualizes the CPU information for each host individually.
 In this dashboard, there is again a link at the top back to the overview, simply achieved using a [.guihint]#Static text# dashlet.
 
+.The return path in the top-down dashboard is via manually-edited text links
 image::dashboard_topdown2.png[alt="Link to return to the calling dashboard."]
 
 With such cross-links, you can develop complex research tools via dashboards.
@@ -603,7 +632,8 @@ The solution to this problem is trivial
 -- alter the service filter and the selected metric in the dashlet configuration.
 Of course, this also applies to all other dashlet variants.
 
-
+////
+// ML: Den Fehler scheint es nicht mehr zu geben (Elemente bleiben einfach leer), es geht um Views, nicht Dashlets, die Namen haben sich geändert
 ifdef::onprem[]
 [#host_problems]
 === Empty dashlets: Total host/service problems
@@ -628,3 +658,4 @@ This ensures that the correct data is actually output.
 The solution is simple:
 Create a new connection with the correct ID.
 endif::[]
+////

src/common/en/intro_gui.asciidoc

@@ -87,9 +87,11 @@ locations on the {CMK} interface, such as in the [.guihint]#Overview# or here on
 right in the first line of the [.guihint]#Monitor# menu:
 
 ifdef::onprem[]
+.Three points (...) are used to reduce complexity in {CMK}.
 image::intro_monitor_menu_showmore.png[alt="First line of the Monitor menu with search input field and Show more symbol."]
 endif::[]
 ifdef::saas[]
+.Three points (...) are used to reduce complexity in {CMK}.
 image::intro_monitor_menu_showmore_saas.png[alt="First line of the Monitor menu with search input field and Show more symbol."]
 endif::[]
 

src/common/en/user_interface.asciidoc

@@ -153,10 +153,10 @@ endif::[]
 You can customize and extend elements of the graphical user interface that are useful for monitoring in the [.guihint]#Customize# menu:
 
 ifdef::onprem[]
-.The [.guihint]#Customize# menu of {CE} in Show more mode
+.The [.guihint]#Customize# menu of {CE} in show more mode
 endif::[]
 ifdef::saas[]
-.The [.guihint]#Customize# menu in Show more mode
+.The [.guihint]#Customize# menu in show more mode
 endif::[]
 image::customize_menu_more.png[alt="Customize menu in the navigation bar.",width=65%]
 
@@ -182,11 +182,11 @@ In some lists you will find _built-in_ objects delivered with {CMK} that you can
 Your entry point to the xref:wato#[configuration of {CMK}] is the [.guihint]#Setup# menu, which you can open via the navigation bar:
 
 ifdef::onprem[]
-.The [.guihint]#Setup# menu of {RE} in Show less mode
+.The [.guihint]#Setup# menu of {RE} in show less mode
 image::setup_menu.png[alt="Setup menu in the navigation bar."]
 endif::[]
 ifdef::saas[]
-.The [.guihint]#Setup# menu in Show less mode
+.The [.guihint]#Setup# menu in show less mode
 image::setup_menu_saas.png[alt="Setup menu in the navigation bar."]
 endif::[]
 
@@ -213,6 +213,7 @@ include::include_searching_in_the_configuration_environment.asciidoc[]
 
 In the [.guihint]#User# menu you can change personal settings that are valid for your user account:
 
+.Changing personal settings in the [.guihint]#User# menu
 ifdef::onprem[]
 image::user_menu.png[alt="User menu in the navigation bar.",width=65%]
 endif::[]
@@ -287,6 +288,7 @@ After logging in, you will first see the standard or main dashboard.
 The content of the main page changes depending on your selection in the navigation bar and also in the sidebar. 
 For example, if you select [.guihint]#Hosts > All hosts# in the [.guihint]#Monitor# menu, the list of hosts will be displayed on the main page:
 
+.Opening the host overview in the [.guihint]#Monitor# menu
 image::mainpage_all_hosts.png[alt="Main page with list of all hosts."]
 
 Regardless of which page is currently displayed, you will usually find the following elements on the main page:
@@ -372,10 +374,12 @@ Every user can nonetheless still create and manage their own bookmarks.
 
 With the [.guihint]#Bookmarks# snap-in you can access the management of the bookmark lists:
 
+.Managing the bookmark list via the [guihint]#Bookmarks# snap-in
 image::user_interface_bookmark_lists.png[alt="Bookmark lists."]
 
 You can now either edit an existing list with icon:icon_edit[alt="Icon for editing a list entry."] -- or create a new one with [.guihint]#Add list#:
 
+.Adding a new bookmark
 image::user_interface_new_bookmark_list_general_properties.png[alt="Dialog with properties when creating a bookmark list."]
 
 In the [.guihint]#General properties# box you enter the internal ID and the title of the list -- whereby the [.guihint]#Title# is not important for the display of the bookmarks, it is only used for management. 
@@ -389,6 +393,7 @@ The principle of visibility is used by {CMK} in many locations, and is explained
 
 In the [.guihint]#Bookmarks# box you can now define the new bookmarks with a title and URL:
 
+.Creating new bookmarks in the [.guihint]#Bookmarks#
 image::user_interface_new_bookmark_list_bookmarks.png[alt="Dialog for setting the properties for the new bookmarks."]
 
 Where the bookmarks are sorted is decided by the [.guihint]#Default Topic# in the list, or respectively by a bookmark’s [.guihint]#Individual Topic# -- if this has been set.
@@ -397,6 +402,7 @@ Finally, save the new list with [.guihint]#Save & view list#.
 
 The new list created in this example now supplements the personal bookmarks under [.guihint]#My Bookmarks# for all users with three bookmarks on two new topics:
 
+.Personal navigation via bookmarks
 image::user_interface_bookmarks.png[alt="Bookmarks snap-in with the three newly created bookmarks.",width=50%]
 
 

src/includes/en/include_searching_in_the_configuration_environment.asciidoc

@@ -10,8 +10,10 @@ You do not need to pay attention to upper and lower case.
 The search results are displayed as you type:
 
 ifdef::onprem[]
+.Free text search in the configuration environment
 image::gui_setup_menu_search.png[alt="Setup menu with search results.", width=65%]
 endif::[]
 ifdef::saas[]
+.Free text search in the configuration environment
 image::gui_setup_menu_search_saas.png[[alt="Setup menu with search results.", width=65%]
 endif::[]

src/includes/en/include_searching_in_the_monitoring_environment.asciidoc

@@ -3,6 +3,7 @@ include::global_attr.adoc[]
 In the [.guihint]#Monitor# menu, you can search for hosts, services and [.guihint]#Monitor# menu entries.
 The search is interactive, so as soon as you have typed something, you will immediately see the results matching your input below the search field:
 
+.Interactive search in the [.guihint]#Monitor# menu
 image::gui_monitor_menu_search.png[alt="Monitor menu with search results.",width=65%]
 
 The search function in the [.guihint]#Monitor# menu is identical to that offered to you by the [.guihint]#Quicksearch# snap-in.