handling the monitoring templates and assignment

8/17/2019 Handling the Monitoring Templates and Assignment

1/10

Monitoring metrics are grouped into templates. The templates are then

assigned to the systems.

Basis Admin team, pls do not touch the monitoring template in the step 4

below. This needs to be handled with care or there could have errors. The

screenshot here is for your info.

Example of Template for Database (Non Production MSSQL Server).

Tis template is assi!ned to man" s"stems# e! D$%.


2/10

&n te above screen# "ou can see te templates tat are assi!ned to D$%. 'ne of

tem is NonProduction MSSQL Server template.

The current available templates that are setup are:

Tese database templates are assi!ned to all our s"stems on MSSQL. Te" contain

MSSQL metrices.

Tese Maxdb database templates are assi!ned Livecace and LSE * s"stems.

Te" contain Maxdb metrices.

Tese *indo+s templates are assi!ned to te s"stems in +indo+s. Te" contain

+in metrices li,e cpu# memor" metrices.


3/10

Tese Linux templates are assi!ned to te LSE * Te" contain +in metrices li,e

cpu# memor" metrices.

Tese -bap templates are assi!ned to s"stems +it abap stac,s. Te" contain /

metrics li,e oll area# ac,!round 0ob 1ueue# / availabilit"# etc.

Tese $ava templates are assi!ned to s"stems +it 0ava stac,s. Te" contain $ava

metrices li,e S"stem Treads 2sa!e# -plication Treads 2sa!e and $ava ttp

availabilit".


4/10

Tese -bap templates are assi!ned to s"stems +it -bap stac,s. Te" contain -bap

metrices tat are not coverd in te earlier --P T& templates. Tis templates

contain 32pdate Process Status4# 3Spool Num an!e4.

Tese Livecace templates are assi!ned to te Livecace s"stems. Te" contain

metrices li,e Livecace status# 5eap usa!e# Data 6ace usa!e.

Sometimes# +e ma" need to stop a component of a s"stem frombein! monitored

(e!# +e don7t +ant te memor" bein! monitored in P$% ma"be because te memor"

is al+a"s expectedl" i! above 89).

Scenario% : 2nassi!n te template +ere memor" is from te s"stem. (asis -dmin

team can andle tis).


5/10

(*en a template is unassi!ned from a s"stem# all te metrices in te template +ill

also be unassi!ned from te s"stem.)

;oto PM tcode 3solman De?ne Scope.

Select te ro+ for P$% and clic, 3next4.

6lic, 3Edit4 and ten remove te *indo+s Template from te assi!nment. Te

*indo+s template contain te Pa!in! memor" metrics.


6/10

Do tis for all servers of P$%.

Te 3-ppl" all Mana!ed S"stems4.


7/10

Scenaro @: Deactivate te metric from te template tat is assi!ned to te s"stems

(asis -dmin team# pld don7t7 touc ere).

(*it tis metod# all te s"stems tat te template is assi!ned to +ill also not

ave tis metrics).

;oto tcode 3solman


8/10

;oto 3Mana!ed 'b0ects4 tab and ten 3-ppl" to all mana!ed s"stems4.


9/10

Sometimes, we need to change the threshold of a metric. Basis Admin, pls

dont touch here.

;oto 3solman


10/10

;oto te metric and te tresold. 6an!e te values and ten save.

;oto 3Mana!ed 'b0ects4 tab and ten 3-ppl" to all mana!ed s"stems4.

handling the monitoring templates and assignment

Documents