System Center Operations Manager

I suggest you ...

← General Operations Manager Feedback

LogEndToEndEvent.js/ps1 CPU impact

Almost like https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback/suggestions/18601399-reduce-cpu-impact-for-scompercentagecputimecounter

the interal health check script runs on all monitored computers at the exact same time. Please find a way to reduce the VM host CPU overhead this causes.

Script:
http://systemcenter.wiki/?GetElement=Microsoft.SystemCenter.AgentManagement.LogEvent&Type=WriteActionModuleType&ManagementPack=Microsoft.SystemCenter.2007&Version=7.2.11719.0

13 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    Martin Ehrnst shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Forgot password?
      Create a password
      Signed in as (Sign out)
      Close
      Close
      Submitting...
      • Martin Ehrnst commented  ·   ·  Flag as inappropriate

        Confirmed by MS Premier Support. This rule does not do anything else than to log the event. The monitors using the event are disabled by default. It is totally safe to disable, and as long as you have *any* other event collected by SCOM you have confirmation of event collection work

      • Martin Ehrnst commented  ·   ·  Flag as inappropriate

        Hi Kevin, yes, we noticed the cpu impact on our hosts. Managed to track it down to that particular script using perf.mon etc. over a few hours. Not a problem for a single VM but for a host you will see CPU wait time etc caused by this as all VM's want to run at the exact same time.

        Added a few screen shots. one for a VM and one for the host who struggle the most

        VM: https://pasteboard.co/GSZjJRQ.png

        Host: https://pasteboard.co/GSZkoLd.png

      • Kevin Holman commented  ·   ·  Flag as inappropriate

        Are you actually seeing CPU impact here in practice, or in theory? Because the simple writing of an event is VERY low CPU impact. Like difficult to measure, low.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Could probably change:
        Microsoft.SystemCenter.AgentManagement.LogEndToEndEvent

        From :
        <DataSource ID="Scheduler" TypeID="System!System.SimpleScheduler">
        <IntervalSeconds>900</IntervalSeconds>
        <SyncTime>01:00</SyncTime>
        </DataSource>

        To(will need to allow some overrides or hardcode the values instead):

        <DataSource ID="Scheduler" TypeID="System!System.Scheduler">
        <Scheduler>
        <SimpleReccuringSchedule>
        <Interval>$Config/IntervalSeconds$</Interval>
        <SpreadInitializationOverInterval Unit="Seconds">$Config/SpreadTimeSeconds$</SpreadInitializationOverInterval>
        </SimpleReccuringSchedule>
        <ExcludeDates />
        </Scheduler>

      General Operations Manager Feedback: General

      Feedback and Knowledge Base

      (thinking…)