BigFix Self Monitoring

Content Authoring
1

Hi, i would like to share information regarding bigfix self monitoring for core infra

Purpose:

BigFix can now monitor its own attributes (RAM, CPU, Disk, core services, etc.) without requiring an external monitoring tool.

Tools Used:

BigFix + ITSM (Incident Management)

Workflow:

  1. A BigFix Fixlet sets the threshold values for the desired services or attributes to be monitored.
  2. BigFix schedules self-monitoring to periodically check the threshold values.
  3. If a threshold breach is detected, an incident is automatically triggered and assigned to the BigFix Admin group.
  • Alerts remain on hold until the current issue is resolved, ensuring that no duplicate incidents are created for the same issue.
  1. The BigFix Admin resolves the incident and fixes the issue.
  2. A second Fixlet is executed to automatically close the incident with relevant work notes.

Benefits:

  • Enables self-monitoring, reducing dependency on external monitoring tools.
  • Addresses the needs of mid-range customers who prefer not to invest in separate monitoring tools for BigFix infrastructure.

image
image627Ă—736 50.1 KB

Pls find the .BES files below to execute to fixlets

  1. Bigfix Monitoring
  2. Bigfix ITMS incident closure

download .bes file from the github link

image
image1462Ă—888 38.8 KB

image
image761Ă—350 34.7 KB

2 Likes
2

This is not going to look good formatted for the Forum. I’d suggest you upload your content to BigFix.me or to a GitHub repo, and then link it here with a description…and thanks for sharing!

3

how to upload in bigfix.me ? i would rather create a github link

thanks for the suggestions

4

@mail2vij, just so I understand this is something you’ve put together on your own and sharing with the community on “use as is” integration/solution?

5

you need to change the fixlets as per your ITSM tool / connection

6

I get that where I was getting to this is very basic - pretty much any server should have some basic monitoring which would cover RAM/CPU/Disk/core services so I would consider this pretty much “basic server monitoring”, not “BigFix monitoring”. Don’t get me wrong, glad you are sharing it and it can be useful for small clients without enterprise-level tools but doesn’t go to the level required for critical enterprise-level tool.

What is really required is advanced system KPIs that are monitoring for errors in relay/root server logs; download errors; cert errors; other client errors; gather errors; filldb errors, sql errors, operator errors; etc. Something you just get as a package add it to the monitoring system of choice and have comprehensive system-level monitoring to proactively detect issues, not to mention that modern monitoring systems can do predictive failures based on KPI patterns of reoccurrences/growth.

There are a number of ideas on the topic but nothing available as far as I know: