Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tuning dashboard new version #610

Merged
merged 4 commits into from
Dec 11, 2020

Conversation

MalloZup
Copy link
Contributor

@MalloZup MalloZup commented Dec 3, 2020

Add new dashboard according expected layout

image

@MalloZup MalloZup changed the title WIP: improve tuning dashbaord Tuning dashboard new version Dec 7, 2020
Copy link
Collaborator

@arbulu89 arbulu89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MalloZup It looks much much better. Well done.

But... Some personal opinions (as always hehe):

  • I would use the next columns order. host|sap note|description|status
  • I would just put the colored box in the status
  • The column names don't have the same structure. Some have just capital letters, others not (check the 1st table). And I would put complete text. s/SAP NOTE DESC/SAP Note description

Finally, did you check what we have when the solution/note is not applied? To check the colors and text. Just in case testing hehe

@stefanotorresi
Copy link
Contributor

  • I would use the next columns order. host|sap note|description|status

IIRC Grafana doesn't allow for customizing the column order, it goes alphabetically by default.

@MalloZup
Copy link
Contributor Author

MalloZup commented Dec 9, 2020

there are some points we can't address, mostly because as users we are tempted to consider grafana as normal UI.

  1. the colors: grafana colors the field by threshold values. So if 2 or more metrics have value 1 you can say, colors all 1 to green, 2 to yellow , 3 red. Is not coloring by field Is in this case not a UI.

  2. the solution NOT applied/note is an old problem which is related on how an exporter is build.
    In case of the saptune solution, this could be achieved (Saptune solution_enabled follow-up/improvements saptune_exporter#4)
    In case of the saptune note, that could require much more work * or we need to investigate, if even possible

The question is about 2, since mostly everything need to be redesigned, I think is not even worth the effort

the rest of comments can be adressed, I will need to check thx!

@stefanotorresi
Copy link
Contributor

stefanotorresi commented Dec 9, 2020

@MalloZup try to address everything that can be addressed before the end of the current sprint and open a followup issue for the remaining point.
We'll most likely need to fix that issue in the MVP, we cannot just postpone this to the superseding project: the MVP should show which SAP notes and solutions are not applied. If that means working on the exporter, so be it.

@MalloZup
Copy link
Contributor Author

MalloZup commented Dec 9, 2020

yes, I will adress the comments one by one and follow-up other things which require more work in follow-up issues, as usual.

thx 👍

@arbulu89
Copy link
Collaborator

arbulu89 commented Dec 9, 2020

The question is about 2, since mostly everything need to be redesigned, I think is not even worth the effort

@MalloZup I didn't understand the answer from question 2. Do you mean that we cannot show the notes that are not applied?
That would be quite bad... But if don't have any alternative. Right now, the exporter is only sending metrics for applied notes? And not for the not applied?

@MalloZup
Copy link
Contributor Author

MalloZup commented Dec 9, 2020

@arbulu89 regarding the note not enabled I think we need to search bit.

saptune note list

All notes (+ denotes manually enabled notes, * denotes notes enabled by solutions, - denotes notes enabled by solutions but reverted manually later, O denotes override file exists for note):
	1410736		TCP/IP: setting keepalive interval
			Version 6 from 13.01.2020 
	1557506		Linux paging improvements
			Version 14 from 10.08.2015 
	1680803		Sybase - SAP Adaptive Server Enterprise
			Version 24 from 20.11.2017 
 *	1771258		Linux: User and system resource limits
			Version 5 from 18.06.2018 
	1805750		SYB: Usage of HugePages on Linux Systems with Sybase ASE
			Version 6 from 14.11.2017 
 *	1980196		Setting Linux Kernel Parameter /proc/sys/vm/max_map_count on SAP HANA Systems
			Version 7 from 18.10.2017 
 *	1984787		SUSE LINUX Enterprise Server 12: Installation notes
			Version 35 from 29.11.2019 
	2161991		VMware vSphere configuration guidelines
			Version 26 from 02.12.2019 
 *	2205917		SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12
			Version 57 from 23.04.2019 
 *	2382421		Optimizing the Network Configuration on HANA- and OS-Level
			Version 36 from 16.01.2020 
 *	2534844		Indexserver Crash During Startup due to Insufficient Shared Memory Segment
			Version 12 from 15.11.2017 
 *	941735		SAP memory management system for 64-bit Linux systems
			Version 11 from 04.05.2018 
	SAP_BOBJ	operating system tuning for SAP Business OBJects (BOBJ)
			Version 0 from 10.03.2017 

@angelabriel is this ok if I would assume that the notes without a * are the not enabled?

In that case we can have the not enabled note metric, but we need to change a bit the code who is parsing that.

@angelabriel
Copy link
Contributor

angelabriel commented Dec 9, 2020

@angelabriel is this ok if I would assume that the notes without a * are the not enabled?

In that case we can have the not enabled note metric, but we need to change a bit the code who is parsing that.

yes, that assumption is true.
There are 2 possibilities:

  1. use 'saptune note list' and parse the output
    or
  2. use the function 'note.GetTuningOptions(NoteTuningSheets, ExtraTuningSheets)'. Here you get a structure, which contains all available note definitions (from saptune and the custom specific). With the knowledge of the 'enabled' notes, you can extract the 'non enabled' notes.
    But as discussed some days ago, the saptune functions were not designed as an external API and may be changed in future releases. So this can be a short term solution for a 'demo', but for a solid solution we should work on the definition of the new saptune API based on 'json' files. Sören is currently working on some definitions and we should setup a meeting/workshop early in January next year to define together all the needed requirements to make it easy to use and stable

@stefanotorresi
Copy link
Contributor

Do you mean that we cannot show the notes that are not applied?
That would be quite bad... But if don't have any alternative. Right now, the exporter is only sending metrics for applied notes? And not for the not applied?

@arbulu89 yes, precisely. That's due to the design issue in the exporter mentioned above.

@MalloZup
Copy link
Contributor Author

@MalloZup
Copy link
Contributor Author

@stefanotorresi @arbulu89 please review this.

Follow-up issue are:

on the exporter side.

After that we can release the exporter to packagehub. updating jira

Copy link
Collaborator

@arbulu89 arbulu89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks nice @MalloZup

I would just rename the table headers to:
s/Saptune solution enabled/Applied profile
s/Current profile/Profile
s/SAP Note/Applied SAP notes/

But the current ones can work too. We will review them in the next group review.
Thanks again

@MalloZup
Copy link
Contributor Author

@arbulu89 I took some names by the presentation we did in past I don't mind to change.

I applied the change on latest commit.

image

@MalloZup MalloZup merged commit 647bea9 into SUSE:sap-blue-horizon Dec 11, 2020
@MalloZup MalloZup deleted the sap-blue-tuning branch December 11, 2020 09:44
@MalloZup
Copy link
Contributor Author

everything is adressed on latest commit a part of the exporter tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants