New Management Pack releases and change tracking
When the OpInsights team releases new IPs/MPs they're automatically downloaded and executed on agents. While I'm sure you're performing all the tests needed, there can be disruptions on the agent side, just like it happens with OpsMgr. The main difference is that with OpsMgr the admin is in full control, with OpsInsights it is not. You should give the user a way to track MP changes, a few ideas:
- use the change tracking IP and add MP tracking
- use a newsfeed / tile on the portal with the latest release for every IP and core management packs. It should state the release date and a short abstract of what has changed.
It would be great to have both :-).
Thanks for the idea, Daniele.
What would be the purpose of having such information? What would be the use cases of such information when the user is unable to revert the changes?
nice post, this post is helpful for me, I got what I came for with accurate information, also see https://myupbeat.com thanks
cool post, this post is helpful for me, I got what I came for with accurate information, also see <a https://axeadvice.com> thank you
With Azure Automation’s Change Tracking and Inventory solution, you can collect and inventory information on installed software, files, Linux daemons, Windows Services and Windows Registry keys on Azure and non-Azure machines. In this Snip, Matt will demonstrate how to enable the Change Tracking and Inventory solution for an Azure Automation Account. Once enabled, we will walk through the steps for onboarding both Azure VMs and non-Azure machines. Then we will move on to configuring the Inventory items that we will be tracking changes for (Windows Registry, Windows Files, File Contents and Windows Services). Finally, we will use a Log Analytics query to return inventory results based on certain criteria. https://www.topshadesailsgoldcoast.com/
Change Tracking doesn’t send every change over the wire. With a technology like transactional replication, every change that’s made is sent off into replication. If I update a single row a million times, that usually means at least a million “commands” head off into my distribution database. But I don’t always want all of those values. Often, I just want the most recent value, so Change Tracking offers a lightweight solution.
2. Change Tracking doesn’t care what platform your client is running. With a technology like merge replication, all the partners need to run merge replication. With Change Tracking, your client application just needs to come in and talk to a web server. The web server then queries out data that’s changed and sends it back to the client. The client doesn’t need to know a thing about SQL Server. (Clarification: there’s a part of merge replication itself which is also called “Change Tracking”. That’s totally different than what I’m talking about in this post.)
These management packs have been changed so that they now require Microsoft SQL Server 2017+ Core Library of version 22.214.171.124, which is delivered within these management packs as well as within the management pack for Microsoft SQL Server 2017+ of version 126.96.36.199
In your Automation Account, select Change tracking under CONFIGURATION MANAGEMENT. Click Edit Settings (the gear symbol). On the Change Tracking page, select Windows Files, then click + Add to add a new file to track.
You can also install Vshare For PC (Windows/Mac):
Run Nox App Player emulator (you may be required to sign in with Google ID)
Go to the folder where you have downloaded the APK file for the app.
Drag the file and then release it anywhere onto the Nox emulator interface.
and download from https://vshare.ninja/
The Change Tracking solution helps you identify software and ... domain controllers · Azure Information ProtectionBetter protect your .... Azure Automation Change Tracking tracks changes in virtual .....
Zim Ali commented
Microsoft System Center Management Pack (Release Candidate 1) for SQL Server 2017+ Replication enables the monitoring of Replication as a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between the databases to maintain consistency.
Ian Pickering commented
IMHO, just like allowing OpsMgr to download & install MPs from the MS web service, it is poor admin practice to deploy new MPs without any change control. It would be great to be able to see the MP guide before any new MPs are released into OMS.
B Carlson commented
We may not be able to revert changes, but at least we'd be able to use OMS for what it's good at, Analyzing our environments to determine "What recently changed, and who did it?"
The goal is to able to understand if an issue root cause can be related to a newly released MP. Take for example the issues we're facing with the latest wire data MP, it took some time to correlate the CPU spikes with the MP release. Let's say I have my CPU perf in OpInsights and I can see when the spike started, then I can time window into change tracking and see what's happened. 2' and I have a possible cause across al my systems.
On the other hand, you're right I cannot do anything except open a support call, and this is anothjer topic I'm going to post: give us the ability to revert to a last known good configuration, or stage updates. Today I had to remove the WireData MP that was killing the DCs, this has been possibile since we're just evaluating the module, but if it happens once in full production? Not a good situation to be in, for the customer and for OpInsights credibility. OpInsights is susceptible to bad MPs as SCOM is, the difference is with SCOM I can always revert, I can have a staged process, multiple MGs, in a way or another I'm able to limit the damage.