Solution Manager 7.1 monitoring content update
I encountered a problem where the diagnostics agents self-monitoring was not reporting into the technical monitoring alert inbox.
After you have set up the monitoring in Solution Manager and the Solution Manager self-monitoring is active, alerts should be pushed into the Technical Monitoring alert inbox when an agent becomes unavailable.
If it works properly you would get an alert as shown in picture 1.0. If you select the alert and open up the alert details (see picture 1.1) then you should get the details on the agents that are connected to Solution Manager and which of those has been down and is down at the moment.
What was I getting? Nothing at all. I could see in the agent framework that an agent would be down and I could even see in the self monitoring in Solution Manager that an agent would be down but no alerts where being triggered. The solution apparently was updating the monitoring content in Solution Manager 7.1 and then rerun the configuration for self monitoring after applying the content update.
There are some interesting particular things about the monitoring content update and because of that I decided to post this blog.
Updating the monitoring content
GO to transaction SOLMAN_SETUP and choose Technical Monitoring in the left side menu. Next choose the System Monitoring option button under Technical Monitoring (see picture 1.2).
Go to setup step 2.8 Update Content (see picture 1.3)
Note the icon under Source of Import on picture 1.4. This icon implies that the content was delivered through a transport request (in this case most likely the application of SPS04).
Now go into edit mode (see picture 1.5)
Click on Import Content (see picture 1.6)
If you have a Solution Manager that has the same content version installed as mentioned in the message box please ignore that fact and press Yes (see picture 1.7). I hope I’m not the only person to whom this sounds strange and not logical but apparently differences can exist between Content-Version 7 and Content-Version 7 (notice the date uploaded by SAP at in picture 1.6).
Here we go again, confusion, once the content is imported it is not yet applied however, when you look at the table you see Applied (see picture 1.8) but that’s the applying of the content on the date stated under When Applied so in fact the newly downloaded templates are not applied. Try to stick with me on this one, although the content is not yet applied, the mere import of content can fix problems! Yes! That’s so strange right? Hell yes but it’s a challenge to work like this right!
So now you still have to apply the new content. The Apply button offers two options, Apply Directly and Apply with Analysis (see picture 1.9). Apply with Analysis will basically give you a screenshot of the templates that will be removed and the templates that are being added (see picture 2.0) while Apply Directly will just apply the content.
After applying the content you have to see a line in the log (lower right pane) that the content version has been applied (see picture 2.1).
How did I discover the root cause which caused the fact that the self-monitoring was not reporting properly? I didn’t. Howcome? The whole place was lit up green and I didn’t find any useful information in logs or traces. If everything has a status “OK” and “VALID” one doesn’t really expect that something is wrong.
A customer message was created to get this problem solved as none of the logs or traces showed any useful information. The customer message went through to the development level and apparently a specific person had to be contacted to get the problem solved. The advice by SAP support to update the content was the right one though so from a support perspective I’m glad to see SAP support picked it up and solved the issue.
From a technical consultants point of view the whole notion of having a problem on which you can find basically nothing is frustrating. I hope this blog can serve it’s purpose and help out other customers / partners who encounter similar problems.
Thanks a lot for the wonderful Instant guide. It is very clear. I will check this in my system and I will update you!!
Thanks for your comment!
Thanks a lot for your instructions on Content Update, can you please let me know if we update from one content version to next content verion, will this effect already configured CUSTOM templates?
Please let me know
Sry for the late reply, I missed this comment in my communication channel somehow.
You can see where the content update might have impact through the Apply with analysis functionality.
It wouldn't make sense that this would overwrite your custom templates but please check through "Apply with analysis". Only after confirmation would the impacted template get overwritten.
very good blog and without knowing this information i probably wouldnt have been able to complete the step and configure monitoring.. 🙂
I have a question about the Template which are using for the Technical monitoring. That is, can be able to download the existing SAP delivered or custom template from the system. If possible, please share the procedure. Also, is it available best practices template in the SMP download area?
The standard templates are what SAP provides as "best practice" to start from actually. This means that updating the monitoring content (the steps described in the blog post) are all you need to have the latest template updates (besides regularly applying SP's to your Solution Manager for bug fixing / new features).
Which template is used for which system depends on the product version/definition of your managed SAP system(s) in SAP Solution Manager (LMDB, ...).
You can create custom templates based on the standard templates delivered from SAP.
The following document will show you how you can create a custom template (page 11 is the exact spot). The document also shows how you could create your own monitoring element based on CCMS metrics for Technical Monitoring:
On page 12 you see a button "Generate request" which can then be used to place the template that you create in SAP Solution Manager development into a transport request which you can then release and import throughout your landscape so it ends up in production.
Training is also available from SAP: E2E120 Technical Monitoring course - 3 days
Hope this covers your questions.
Thank you for the detailed reply. But trying to generate request for a single custom template, the custom template is not available in the selection list. See below.
Are you sure about that? Custom Templates are by default named "Derived From <source template>" and I do see those in that list you post here. So perhaps your custom template is there without you realizing it.
If not it might be a bug but it's definitely not something I have come across.
We have renamed the name "derived" to our customer name. I am sure these customer named templates are not available in the list.
Well, that could be the issue right there that the template is still listed by the initial (old) name.
Can you verify that those "Derived by" templates also still existing or if you can match the template that you created & renamed to one of those?
Not saying that it should be like that... because that would seem incorrec/strange. Just a thought.
I found that the name "Derived" will be changed to custom name. If we specify a package name, then the custom Template will be available in the list. Hence we can generate request.
Good to hear it works now!
Apart from patching Solution Manager to get the latest content, is there a download area on SMP where you can grab the latest content XML file? The functionality is there in Expert Mode. We are on a secure site with no connection to SAP.
I'll try to find out for you and I'll come back on this question.
Many thanks for your help.
nice document, thanks for sharing
This is updated in SP10 to only have the update as the only option, and it appears to apply this when you tell it to download the content.
Indeed, it got simplified which is good 🙂
Maybe they read the blog, who knows 😉
Manually going to 2.7 step of Technnical monitoring/System monitoring and checking if for any latest updates, Instead of checking every now and then, can we automate this process??
Without going to that step can we check some where else if new content update is available?
FYI - We are on SP10 solman 7.1
In theory anything is possible right but the question is, what's the effort. You could try to trace what is triggered when you push the "update" button and then automate that ~ Z program or Z job or whatever depending on what comes out of the trace.
Another option, although I haven't tried it yet, could be to record the update steps and play them back periodically ~ thinking CBTA (component based test automation).
I'm not aware of any easy, efficient way to be automatically pinged when the content is updated.