-
Notifications
You must be signed in to change notification settings - Fork 0
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
Volatile Properties #7
Comments
Hi @PChipVIA , thanks for your kind feedback. I am aware of the volatile properties and also that it's not a best-practice to do so. As the discovery only runs every 4 hours and the data which is changed is small I believed that there is more benefit than disadvantage by providing the information so that you can get this information at glance in the state view. Have you noticed any negative performance impact on the database or on the agent machine after importing the MP? After reading Brians article again I think collecting the size via rule might be also quiet interesting. Thank you!! 👍 I'll consider you suggestions. |
Hi @Juanito99 , For the volatile properties, I think the entire record updates if a single property changes so IMHO the cons outweigh the pros. Collection Rule indeed would be best as it would allow one to see growth/trends over time. I haven't installed the MP, just wanted to reverse engineer how you detected Tomcat servers and how you detected the log folder... 👍 Learn every day! If I can add a little more to the thread. Couple things
I created a PoC script which addresses the points above (of course there is a need to adjust the classes, relationships & monitoring)
} (sorry first time posting on GitHub, can't seem to figure out the code stuff) |
Hi @PChipVIA, great feedback. Many thanks. If I don't mixup I pulled the log folder out of the registry, or just for Apache ... You are absolutely right about I only cover one instance. Haven't thought there might be multliple. I will check the code when back :-) Second when I am back I will remove the frequently changing properties. Thinking a while longer I think I may be one of the reasons for slowing down our SCOM ... Oops ... As you said learn every day :-) I will update here and would be glad to get feedback after updated later ... Kind regards Ruben |
Hi @PChipVIA , I changed the classes and removed those attributes as suggested. A rule is now recording the size of the log file folders. For the mentioned Tomcat issue I can't find the time at the moment. - Nevertheless, may thanks for this hint! 👍 Ruben |
Hi
Looking at class Windows.Server.Webservice.LogdirectoryWatcher.WebSite.Base, I noticed that it contains at least 4 volatile properties: LogDirModifiedDate,LogDirScanDate, LogDirSizeInMB, LogDirNoOfFiles.
As per https://social.technet.microsoft.com/wiki/contents/articles/14256.operations-manager-management-pack-authoring-classes-and-relationships.aspx#Properties_that_Update_Too_Frequently you should not have properties in classes that change often (as it may cause config churn -- Some post from Kevin Holman). Logically those properties will change every time the discovery will run (every 14400 seconds).
Unless needed, I would recommend you stop discovering them..
HTH
The text was updated successfully, but these errors were encountered: