OE Management: How to disable All System Resource Monitoring - OpenEdge RDBMS - Forum

All Replies

Posted by sgabbeta on 22-Jul-2015 06:40

Hi Valeriy,

You have to disable the resource in OEM to disable monitoring. And this should be done to each resource (in your case system resource) individually.

Thanks

Regards,

Sharath

[collapse]

From: Valeriy Bashkatov [mailto:bounce-Arelav2@community.progress.com]
Sent: Wednesday, July 22, 2015 4:43 PM
To: TU.OE.RDBMS@community.progress.com
Subject: [Technical Users - OE RDBMS] OE Management: How to disable All System Resource Monitoring

OE Management: How to disable All System Resource Monitoring

Thread created by Valeriy Bashkatov

Hello,

Is it possible to disable All System Resource Monitoring permanently even when added to OEM a new container?

In the documentation I have seen the chapter Disabling an individual resource monitor, but this is not what is needed in my case.

Regards,
Valeriy

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

Posted by Valeriy Bashkatov on 22-Jul-2015 07:26

[quote user="sgabbeta"]

Hi Valeriy,

You have to disable the resource in OEM to disable monitoring. And this should be done to each resource (in your case system resource) individually.

Thanks

Regards,

Sharath

[/quote]

Hi Sharath,

But it is not logical.
For example, I have a server with a 128 CPU, I will "die" until I disable each individually. Let's say I did it in the end.

And then I was given one more server with CPU 128 to be connected to the OEM as a container ....

Maybe is somehow possible to disable, for example, the monitoring plan for all CPU? Or is there some kind of decision yet?

Posted by Libor Laubacher on 22-Jul-2015 07:37

I have replied to this but alas again the email parser did not deem my post worth parsing for the MNth time.

> For example, I have a server with a 128 CPU,

1) change it on 1 CPU

2) go to options - resource property distribution and bulk copy this to the rest of 127 CPUs

> the monitoring plan for all CPU?

options - resource monitoring details

Posted by Valeriy Bashkatov on 22-Jul-2015 08:01

Hi Libor,

>>1) change it on 1 CPU

>>2) go to options - resource property distribution and bulk copy this to the rest of 127 CPUs

This sounds more interesting )

I tried it on my desktop first.

I disable CPU-0 then go to Distribute Resource Properties

But I get error after click submit

What I do wrong?

Posted by Valeriy Bashkatov on 22-Jul-2015 08:02

It is OpenEdge 11.5.1 Win 64.

Posted by Valeriy Bashkatov on 22-Jul-2015 08:14

>>options - resource monitoring details

Here is necessary to clear "Trend" field?

Posted by Libor Laubacher on 22-Jul-2015 08:15

> What I do wrong?

Nothing. The tool for whatever reason in its wisdom won't redistribute the properties for a 'disabled' resource. I will log a bug for that.

option 1) set poll interval to something like 365 days and then redistribute it

option 2) do / run something like this

fathom -user admin -password progress -restype system -reslist | grep CPU | awk '{print $2}'

it will give you a list of CPU resources (feel free to fine tune the grep)

then either output it to a file or in for i in `` loop

and parse the output

fathom -user admin -password progress -disable $i

where $i is the list of the CPUs

proenv>fathom -user admin -password progress -disable localhost:resource.system.cpu.CPU-cpu1

OpenEdge Release 11.5.1 as of Wed May 6 18:21:44 EDT 2015

The following resource has been disabled. Resource: CPU-cpu1

Posted by Libor Laubacher on 22-Jul-2015 08:17

proenv>cat disable_cpus.sh

for i in `$DLC/bin/fathom -user admin -password progress -restype system -reslist | grep CPU | awk '{print $2}'`

$DLC/bin/fathom -user admin -password progress -disable $i

done

proenv>./disable_cpus.sh

OpenEdge Release 11.5.1 as of Wed May 6 18:21:44 EDT 2015

The following resource has been disabled. Resource: CPU

OpenEdge Release 11.5.1 as of Wed May 6 18:21:44 EDT 2015

The following resource has been disabled. Resource: CPU-cpu0

OpenEdge Release 11.5.1 as of Wed May 6 18:21:44 EDT 2015

The resource was already disabled. Resource: CPU-cpu1

Posted by Valeriy Bashkatov on 22-Jul-2015 08:42

Fine! this is what I need! Thanks!

I have one more question )

How to disable alert about LogFileNameChanged?

Too many messages about it comes (

Posted by Libor Laubacher on 22-Jul-2015 08:51

You would need to wait for 11.6 for that I am afraid.

Posted by Valeriy Bashkatov on 22-Jul-2015 08:56

Ок. Thank you very much again!

Posted by Satya Prasad on 27-Jul-2015 05:08

As Libor said, This feature(disabling LogFileNameChanged alert) will be available in 11.6 by enabling “Suppress name change alert” option for that particular resource.

Thanks,

Satya

This thread is closed