Big PanDA Monitoring
Introduction
BigPanDA Monitoring Requirements
Draft of monitoring needs for LSST VO
- Summary of activity per PanDA instance (multi-VO summary view)
- VO production summary
- physics group/single user activity summary page
- job properties
- job history
- accounting?
- adjacent activities such as SW installation and data distribution
- logging: server activity, monitor activity; VO specific resources availability: sites, slots, SW, data, ...
All these things are possible to modularize, and can be done VO-independently. When a VO-specific need of change emerges, the models can be extended.
PanDA-Condor interface
Survey of the existing monitor capabilities
Monitoring pages
[1] A single job details page
- (01-01) Status summary table: PanDAID, Owner, Working group; job name, job attempt number, job input/output dataset; job status; timestamp Created, interval "time to start", duration of the job, timestamp Ended/Modified; cloud, siteID; job priority.
- (01-02) File input/output table: filename, type, status, dataset and dispatch block.
- (01-03) Find and view log files.
- (01-04) Log records for job.
- (01-05) Job details table: column name, column value. In order of columns in the table (e.g. jobsdefined4) definition.
- (01-06) Production job: link to "show associated task".
- (01-07) Production job: link to "show recent jobs for task".
- (01-08) Production job: link to "Show script to re-create job for offline debugging".
- (01-09) Production job: show log extract.
- (01-10) Production job: Transformation tags: list of trf tags. Link to "Interpret tags and show transformation configuration".
- (01-11) Associated build job info (if applicable).
- (01-12) Job history: list PanDAID, attempt nr., timestamp Ended/Modified, job name, cloud/site, error summary.
[2] User's activity summary page
- (02-01) Activity statistics: nr. of jobs in past week, job types with nr of jobs per job type, 24h quota (in CPU hours), link to doc with priority degradation, list of groups; usage in CPU hrs for personal analysis/group production in the last 1 day and in the last 7 days.
- (02-02) Filter summary of jobs: selector of job type/all jobs, text field timespan "last N days", text field jobsetID, selector of job status/all jobs, show/hide summary plot, button Retrieve All.
- (02-03) Summary wall: number of selected jobs. Group by states with number of jobs in that state, number of jobs links to filtered page; Followed by several lines, one line per quantity, each line contains number of distinct categories of that quantity, and list of categories with number of jobs per that category. Quantities are: Users, Processing types, Job types, Transformations, Working groups, Creation hosts, Sites, Regions, Clouds, Jobsets; Link to filtered pages "show jobs for last 7/15/30 days".
- (02-04) Button to show/hide table with datasets used by selected jobs: User datasets, type, last used, used in N jobs.
- (02-05) Button to show/hide job sets: user:jobsetID linking to jobset summary page, timestamp Created, timestamp Latest [Q-001], #jobs total (build job included), #jobs in Pre-run, Running, Holding, Finished, Failed, Cancelled, Merging, buildJob status, Site, Input/Output dataset, link to ATLAS Analysis Task Monitor for the input/output dataset.
- (02-06) Information about "showing N jobs from ... to ..." (N <= 1000).
[3] User's jobset summary page
- (03-01) Filter: same filter as in (02-02).
- (03-02) Summary wall as in (02-03).
- (03-03) Table with jobset summary with only 1 jobset, same fields as (02-05).
- (03-04) Information about how many jobs are shown, see (02-06).
- (03-05) Table with jobs summary, one row per job, same info as in (01-01) per job.
[4] Production
- http://panda.cern.ch/server/pandamon/query?dash=prod
- title: Panda Production Operations Dashboard
- contacts:
- help (click to activate) with color schema description
- Servers: CERN:OK Logger:OK
- Active tasks (tbd: over past 12 hours?)
- Active tasks
- list of all clouds, number of active tasks per cloud, e.g. CA: 65
- Bamboo: over past 12 hours
- Jobs updated:
- Jobs updated > 12 hrs ago: activated 57666
- Jobs updated > 12 hrs ago: activated running none
- Jobs updated > 36 hrs ago: transferring 52039
- World Wide Summary:
- MC share used in the task brokerage table:
- Summary plots by cloud:
- Cloud efficiency history:
- Production job summary, last 12 hour
- Main table:
- Job Summary from the MultiCore Sites
- table with ajax fetch of the pandamon.cern.ch/mcore view
- Production blocks active in last 12 hours:
[5] Clouds
- http://panda.cern.ch/server/pandamon/query?dash=cloud
- title: Clouds and tasks
- Cloud status:
- hint: TLo, THi are transfer timeouts for low and high priority jobs
- table1: columns: Cloud, Tier1, Status, Comment, Tasks, TLo days, THi days, Storage used by PanDA, Free space (GB), as of, Workload SI2Kdays, Weight, Nprestage
- table1: one line per cloud
- Fast track
- line with text: Fast track clouds used for high priority tasks: CA:true DE:true ES:true FR:true IT:true ND:true NL:true RU:true TW:true UK:true US:true
- line with text: Clouds used for validation tasks: CA:true CERN:true DE:true ES:true FR:true IT:true ND:true NL:true RU:true TW:true UK:true US:true
- table2: hint: Cloud/site details: nqueue is the queue depth (number of pilots in pre-running states) maintained by the scheduler.
npilots is the current queue depth which should roughly match nqueue.
[6] Incidents
[7] DDM
- panda.cern.ch/server/pandamon/query?tp=main
- title: AutoPilot pilot/scheduler system
- links:
- Recent pilots:
- Queues
- hint: For more compact information covering only the queues used by ATLAS clouds, see the clouds page[http://panda.cern.ch/server/pandamon/query?dash=clouds]
- text: Gatekeepers:196 Queues:578
- Regions: with queue count per region
- Queue tags:
- Queues (table):
- columns: pilots, Queue name, Region: Site, System, Status, Que, Run, Fin, Fail, Abort, Latest, TJob
- pilots: link to e.g. http://panda.cern.ch/server/pandamon/query?tp=pilots&queue=ANALY_AM-04-YERPHI
- Queue name: http://panda.cern.ch/server/pandamon/query?tp=queue&id=ANALY_AM-04-YERPHI
- Region Site: region[http://panda.cern.ch/server/pandamon/query?tp=queues®ion=Armenia], site[http://panda.cern.ch/server/pandamon/query?mode=site&site=AM-04-YERPHI]
- system: e.g. http://panda.cern.ch/server/pandamon/query?tp=queues&system=lcg-cg
- status==offline: greyish background
- virtual queues: aqua bg
- Current pilotScheduler services
- Submit hosts
- Pilot types
[10] Sites
- http://panda.cern.ch/server/pandamon/query?dash=site
- title: Panda Sites
- 196 analysis sites -- click to see content in the table
- 11 installation sites -- click to see content in the table
- 1 pandamover sites -- click to see content in the table
- 109 production sites -- click to see content in the table
- 103 production multicloud sites -- click to see content in the table
- 70 test sites -- click to see content in the table
- 4 test multicloud sites -- click to see content in the table
- table:
[11] Releases
[12] Analysis
- http://panda.cern.ch/server/pandamon/query?dash=analysis
- title: Panda Analysis Dashboard
- hint: The current pathena version is 0.4.35. The current ganga version is 6.0.23. It is recommended you use the current versions.
- Documentation on user analysis with Panda:
- Frequently asked questions:
- hint: Use the hn-atlas-dist-analysis-help e-group to learn about known problems and their reported solutions and to report problems of your own.
- Status of pathena analysis queues: See the wiki page PathenaAnalysisQueues[https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PathenaAnalysisQueues]. See also the analysis site blacklist[].
- Analysis jobs: Listing of analysis jobs[http://panda.cern.ch/server/pandamon/query?job=*&type=analysis]. To look up a particular Panda job by ID use the quick search at left or click a PandaID in the job listing.
- Analysis users: User list[http://panda.cern.ch/server/pandamon/query?ui=users&sort=latest] (also linked at top right, or above if you've logged in) shows analysis usage, ordered by most recent. From there you can go to your page (you're on the list if you've run a Panda job); if you 'log in' you'll get easier access to your page from a new menu at the top of the page.
- Groups: Groups[http://panda.cern.ch/server/pandamon/query?ui=groups] are supported to organize users by role, physics working groups etc. and support collaborative work, accounting rights etc. (Not much used yet.)
- Data access: See the physics data[http://panda.cern.ch/server/pandamon/query?dash=physics] page linked above for infomation on data location, requesting replication of data, and staging data from tape to disk.
- Analysis Summary by Cloud: link to [http://gridinfo.triumf.ca/panglia/bycloud/]
- Analysis Summary:
- Analysis summary: similar to Production summary:
- Analysis job summary at 02-26 10:51, last 12 hours (Details: errors[http://panda.cern.ch/server/pandamon/query?overview=errorlist&type=analysis&hours=12], nodes[http://panda.cern.ch/server/pandamon/query?overview=wnlist&type=analysis&hours=12]) pathena analysis queue status[https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PathenaAnalysisQueues]
- Processing types: list of types with numbers of jobs
- Working groups: list of WG with numbers of jobs
- Special Handling: list of special handlings with number of jobs
- hint: Pilot counts are for the last 3 hours. Error rates above 20% are shown in red.
- table with cloud/resource summary, similar to the one in Production view
- Analysis job error report, last 12 hours
- Job wall time: 347272 hrs Error losses: trans: 20523 (5.9%) panda: 13575 (3.9%) ddm: 7662 (2.2%) athena: 8600 (2.5%) user: 2251 (0.6%) other: 297 (0.1%)
- table:
- columns: Error type (type count), Count, CPU-hrs, Latest, Code:, Description, Version Tag
- blocks of the table: ALL + line per error type, resource + line per error code per resource
[13] Stats
[14] Users
- http://panda.cern.ch/server/pandamon/query?ui=users
- title: Recent Panda Analysis Users
- Users in the last 3 days : 370; 7: 507; 30: 801; 90: 1066; 180: 1316;
- Usage in the last 7 days: Job count: 2918999;
- Users with >1000 jobs: 282; Users with >10k jobs: 46
- table
[15] Physics data
- http://panda.cern.ch/server/pandamon/query?dash=physics
- title: Panda Physics Data Dashboard
- hint: ATLAS data discovery and access info and tools for physicists
- Data location and replication status (See also the Datasets Distribution section in the left menu)
- Command line data access tools: See documentation for the dq2-ls, dq2-get -f < files> < dataset> etc. tools: [https://twiki.cern.ch/twiki/bin/view/Atlas/DQ2Clients]
- Dataset subscription request form [http://panda.cern.ch/server/pandamon/query?mode=reqsubs0] Use this form to request replication of datasets Status of requested dataset subscriptions [http://panda.cern.ch/server/pandamon/query?mode=listPatterns]
- Report ATLAS data management operations issues to Savannah [https://savannah.cern.ch/bugs/?group=dq2-ddm-ops]
- User dataset space usage in US [http://www.usatlas.bnl.gov/dq2/monitor/findUserUsage]
- Dataset search by name:
- hint: (left bar) enter dataset name and hit return to bring up an info page on dataset of interest. This search does not support wildcards. For wildcard searches use the search form...
- Dataset query form [http://panda.cern.ch/server/pandamon/query?mode=dbquery]: search by name (with wildcard support) or metadata for matching datasets
- Dataset info pages:
- hint: The above searches lead to dataset info pages which provide info on dataset content, status, production usage, site availability, and access. Info is provided for all datasets defined via production tasks, including those not yet in DQ2. Here's an example [http://panda.cern.ch/server/pandamon/query?mode=dset&name=mc11.005055.PythiaPhotonJet1.recon.AOD.v11000303].
- Data access:
- hint: Dataset info pages provide instructions for data access. Access is via dq2-get -f < files> < dataset>, dq2-ls as documented here[https://twiki.cern.ch/twiki/bin/view/Atlas/DQ2Clients].
- Datasets currently in production [http://panda.cern.ch/server/pandamon/query?days=3&overview=prodlist]: a summary of the input datasets currently being processed by Panda
[16] Left Panel: Jobs
"Search" link
http://panda.cern.ch/server/pandamon/query?mode=dbquery
Leads to a Web form with the following fields:
- Job ID
- Panda ID
- SW Release
- Transformation
- Job Status
- Project
- Scheduler ID
- Creation Time (mm/dd/yyyy). start
- Creation Time (mm/dd/yyyy). end
Summary subpanel
Just like in most blocks of the left panel, the links serve as a quick way to query a URL with slightly varying parameters.
In this case, the tabulated data has the following columns:
Cloud, Pilots, %fail, Latest, defined, pending, waiting, assigned, activated, sent, starting, running, holding, transferring, finished, failed, cancelled, unassigned
Queries appear to contain the 72 hour limit as a parameter by default. Links go to the "platform" mon page.
States subpanel
example - screenshot
[17] Left Panel: Jobs Types
It appears that these are customized search links to expedite queries. The timing cutoff appears to be included in the query, i.e. it's not coded in the service.
Links contain queries of the type
http://pandamon.cern.ch/jobinfo?jobtype=XXX&hours=3&plot=no
, where XXX can take the following values:
analysis, production, prod_test, install, test, retried, jedi, merging, all
Links take the user to the "platform" pages. These pages contain a summary panel on top, which breaks the information down by users, releases, processing types, job types, transformations,
Working Groups, creation hosts, sites, clouds, jobsets.
The job info table that follow the top section has the following columns: User:jobsetID, Created, Latest, Jobs, Pre-run, Running, Holding, Finished, Failed, Cancelled, Merging, buildJob, Site.
Interestingly, the latter contains site names which are links to the old Panda Monitor (i.e. throws back to the original page).
Links summary:
[18] Left Panel: Jobs Timing
This is another interface to a query engine, with the following breakdown (the links present histograms for the past 3 hours)
Pages contain histograms of job execution time distributions:
execute, cpu, setup, stagein, stageout. As is evident from above, queries are basically same, just select on different job types.
example - screenshot
[19] Left Panel: Jobs Metrics
"VM metrics" on top is a link to Wiki:
https://twiki.cern.ch/twiki/bin/viewauth/AtlasComputing/PandaPilot#QaJobMetrics
Other links in this subpanel include the following. As in many other cases, a 3 hour window is assumed by default.
example - screenshot
[20] Left Panel: Jedi tasks
Top Subpanel - Summary
These links present tabulated data with columns:_JediTaskID, status, username, Files, Used, Failed, transUses, transPath, modificationTime, taskname_
In the latter, certificate required for auth. Obviously covers analysis tasks.
Bottom Subpanel - States
Note that 3 day time cutoff is built into the service, not in the URL query.
[21] Left Panel: FAX
There is a single subanel labeled "Summary", which contains:
Fail over:
http://pandamon.cern.ch/fax/failover
Presents a table titled: "Panda report on jobs failovers to FAX over last 6 hours", with the following columns:
Site, Jobs, WithFAX [files], WithoutFAX [files], WithFAX [GB], WithoutFAX [GB]
example - screenshot
Configuration:
http://pandamon.cern.ch/fax/map
An elaborate graphic with a world map and superimposed structure of the graph, representing the FAX network in action (directed arrows etc).
[22] Left Panel: Quick Search
http://panda.cern.ch:25980/server/pandamon/query?tp=main#
There are forms which enable search function by the following parameters:
- Panda job ID
- Panda id by LFN
- Batch ID
- Dataset
- Task request
- Task status
- File
Example of the form code:
< form id="formdsid" action="http://panda.cern.ch/server/pandamon/query" style="margin-top:0; margin:0; border:0; font-size:8pt;" method="GET " >
Dataset
< input id="informdsid" type="text" border="0" maxlength="200" size="6" name="name" tyle="margin-top:0; margin:0; border:0; font-size:8pt;" title="Please fill out this field" >< /input >
< input type="hidden" value="dset" name="mode" >< /input >
< /form >
[23] Left Panel: Errors
Contains links like:
http://pandamon.cern.ch/jobs/joberror?jobtype=production&item=taskID
. All links go to the page "jobs/joberrors". Note that the time
periods in queries are not uniform.
Analysis Users:
example - screenshot - note that the distributions on this page are bar graphs, displaying time evolution of various errors for users
[24] Left Panel: Summaries
Contains a few forms for queries as detailed below:
- Blocks: days (entry field)
- Displays a screen for N days, titled "Production job blocks (destinationDBlock) active in the last N*24 hours. Managed production jobs only"; columns: Destination Block (as a link labeled by the destination block name), subscript - number of jobs in various states, total number of jobs, ATLAS release.
- Errors: days (entry field)
- Nodes: days (entry field). Note: potentially a problematic query, long query times and tons of data, does not scale.
- Displays a screen for N days, with a table listing nodes per site, for N days; columns: All Site, Job, Nodes, Jobs, Latest, defined, assigned, waiting, activated, sent, running, holding, transferring, finished, failed, tot/trf/other
- Usage 1, 3 days:
- Displays breakdown of usage by the cloud, presents a pie chart. Metrics - wall time, jobs, nodes. Same type of info for sites. Further, for each site there is breakdown for wall time per node and wall time per job.
This is a sample HTML code for one of the forms:
< form action="http://panda.cern.ch/server/pandamon/query" style="margin:1px; border:0; font-size:8pt;" method="GET" >
Blocks:
< input type="text" border="0" maxlength="3" size="3" name="days" style="margin-top:0; margin:0; border:0; font-size:8pt;" title="Please fill out this field" >< /input >
< input type="hidden" value="prodlist" name="overview" >< /input >
days
< /form >
[25] Left Panel: Tasks
Top link: "Search":
http://panda.cern.ch/server/pandamon/query?mode=taskquery
.
It's a generic task
and tag search facility, and contains a form, in which a table exposes the following fields:
- Project
- Input Dataset
- Transformation
- Transformation Version
- Grid Flavour (sic!)
- Submitted By
- Output Task Name
- Configuration Tag
- Requested by - selector based on "Group" and "Regional" identity
- Status
- Request ID
- More (?)
- Query Tasks/Tags (selector)
Depending on the type of "Task Req", these links lead to pages formatted accordingly.
Comments to the above table:
- New Tag generates tags based on the following user input
- transformation name
- software version
- production branch
- userid
- function
- Bug Report - quick links to Savannah pages covering Athena, Data access on the Grid, and "Any other problem", which goes to ADC operators.
- Task overview query - a quick query of tasks based on the tag name and a regex in the task name
On the bottom, there is an entry field "clone task". Presumably takes the ID of the task to be cloned.
This function is not robust because it will bomb, for example, if you enter "1", and display diagnostics including some of the server code. This is the code for the form that supports this function:
< form action="https://pandamon.cern.ch/tasks/clonetask" style="margin-top:0; margin:0; border:0; font-size:8pt;" method="GET" >
Clone Task
< input type="text" border="0" maxlength="7" size="6" name="tid" style="margin-top:0; margin:0; border:1; font-size:8pt;" title="Please,provide the TaskID to clone" >< /input >
< /form >
[26] Left Panel: Datasets
"Search":
http://panda.cern.ch/server/pandamon/query?mode=dbquery
- generic form-based search of datasets on the following attributes
- Name
- DataFormat
- Tag
- StartTime (days ago)
- has the option to apply these selectors to Container or Dataset
- Choice of formats for output - summary, object list, object list + file size
Also, the subpanel contains:
[26] Left Panel: Datasets Distribution
Large Section on top of the subpanel - DaTRI. Appears to hit same base query with two varying parameters.
Lower part:
PD2P |
http://panda.cern.ch/server/pandamon/query?mode=pd2p |
link to the "PD2P monitor" page, a table is presented with the following columns: cloud, country, atlas site, ddm endpoint, num ds; there is a selector on top for T1/T2 and the number of days. Site names are links showing tables of datasets |
AODs |
http://panda.cern.ch/server/pandamon/query?mode=listAODReplications |
link to the AOD dataset replication page, where the last 500 replications are listed, and additional filters are available to narrow down the search |
EVNTs |
http://panda.cern.ch/server/pandamon/query?mode=listEVNTReplications |
gets HTTP Error 503 |
Conditions DS |
http://panda.cern.ch/server/pandamon/query?mode=listConditionsDB |
distribution and status of the condition ds, by the cloud |
DB Releases |
http://panda.cern.ch/server/pandamon/query?mode=listDBRelease |
|
SIT pacballs |
http://panda.cern.ch/server/pandamon/query?mode=listPacballs |
|
Validation Samples |
http://panda.cern.ch/server/pandamon/query?mode=listValidationReplications |
|
Functional Tests |
http://panda.cern.ch/server/pandamon/query?mode=listFunctionalTests |
the top portion contains a summary table of test dataset statuses by the cloud; number of files, time metrics for transfer; bottom - large table of datasets; Columns - Tier, Total Datasets, Total Files in datasets, Total CpFiles in datasets, Subscribed, Transfer, Done, Suspect, Deleted, Last Subscription, Last Transfer, Last FC Checked, Average datasets Transfer time |
ATLAS Data |
http://panda.cern.ch/server/pandamon/query?mode=listCR |
same as above but for the data |
Reprocessed_Datasets |
http://panda.cern.ch/server/pandamon/query?mode=listReproDSReplications |
yet another way to query dataset info; nothing is provided in the table by default, but the top portion contains selection fields - cloud and regex for the dataset name; also links to ARDA and DQ2 browsers |
[28] Left Panel: Logging monitor
Single link "Incidents":
http://panda.cern.ch/server/pandamon/query?mode=mon&hours=6
.
Opens a table of the tabulated incidents data, with columns:
- Category (can be blank, but can also be bamboo or prod)
- Type
- Level (e.g. debug, info, warning)
- Count
- First
- Latest
[29] Left Panel: Analytics
[30] Platform Left Panel: Jobs
*Search*
http://panda.cern.ch:25880/server/pandamon/query?mode=jobquery
Summary
Clouds' Summary
Regions' Summary
States
[31] Platform Left Panel: Job Types
Types
[32] Platform Left Panel: Job Timing
Timing:
https://twiki.cern.ch/twiki/bin/viewauth/AtlasComputing/PandaPilot#QaPilotTiming
[33] Platform Left Panel: Jobs' Metrics
VM Metrics:
https://twiki.cern.ch/twiki/bin/viewauth/AtlasComputing/PandaPilot#QaJobMetrics
[34] Platform Left Panel: Jedi Tasks
Summary
States
[35] Platform Left Panel:FAX
Summary
[36] Platform Left Panel:Quick Search
A form for queries, sample code below:
< form action="/jobinfo" style="margin-top:0; margin:0; border:0; font-size:8pt; font-weight:normal;" method="GET" >
Panda jobID
< input type="text" border="0" maxlength="100" size="5" name="job" style="margin-top:0; margin:0; border:1; font-size:8pt;" title="Please fill out this field" >< /input >
< /form >
Forms exist for the following attributes: Panda jobID, Batch ID, Dataset, Task request, Task status, File
[37] Platform Left Panel: Errors
Task Errors:
http://pandamon.cern.ch/jobs/joberror#
[38] Platform Left Panel: Operations
[39] Platform Left Panel: Summaries
Three forms of this kind:
< input type="text" border="0" maxlength="3" size="3" name="days" style="margin-top:0; margin:0; border:0; font-size:8pt;" title="Please fill out this field"> < /input >
The forms are:
- Blocks: days
- Errors: days
- Nodes: days
Links: Usage
[40] Platform Left Panel: Tasks
Top link: Search -
http://pandamon.cern.ch/jobinfo?jobtype=&jobStatus=retried&plot=no#
Form: Clone Task
< input type="text" border="0" maxlength="7" size="6" name="tid" style="margin-top:0; margin:0; border:1; font-size:8pt;" title="Please,provide the TaskID to clone" >< /input >
[41] Platform Left Panel: Datasets
Top link: Search -
http://pandamon.cern.ch/jobinfo?jobtype=&jobStatus=retried&plot=no#
[42] Platform Left Panel: Datasets Distribution
DaTRI:
[43] Platform Left Panel: User
[44] Platform Left Panel: Stats
[45] Platform Left Panel: Dashboards
[46] Platform Left Panel: Logging Monitor
[47] Platform Left Panel: Analytics
[48] Platform Left Panel:New Panda
[Q] Questions
[C] Comments
Query/Mode
Consider
http://panda.cern.ch/server/pandamon/query?mode=listAbortedDatasetsState
. There are plenty of queries that look similar to this one, with "query" mapping onto a Python class or method in all likelihood, and "mode" driving a selector (maybe through an "if" statement. The "query" url seems to be awfully overloaded not in the slightest bit mnemonic. Looking further, this pattern is pervasive and arguably bad design. Cf a completely different domain, which also has
http://panda.cern.ch/server/pandamon/query?mode=dbquery
. This one actually leads to a form. Compare it to:
http://panda.cern.ch/server/pandamon/query?mode=reqtask3
.
Factoring of the query parameters into URLs
Left panel contains a number of subpanels which oftentimes are built as shortcuts selecting a particular parameter in the otherwise identical URL (e.g. x=1 vs z=3). Curiously, the total number of clicks in this design is not reduced compared to a solution where the user navigates to a purpose built query page, from which they can continue with their decision as to what option to use. So this design pattern in the old/platform monitor only creates clutter in the left panel without offering distinct advantages.
Development matters
Major updates:
--
MaximPotekhin - 02 May 2014 - finished the "platform mon" section
--
MaximPotekhin - 21 Apr 2014 - reformatted most entries for the Left Panel as tables, and added a considerable number of URLs
--
MaximPotekhin - 12 Apr 2014
--
MaximPotekhin - 16 Mar 2014: Adding material according to plan
--
JaroslavaSchovancova - 04-Oct-2013
Responsible: TorreWenaus