You didn't miss anything. Similar information is displayed on the Component Details page. This information is not currently available as a resource at the application details level. With some finagling it may be possible to get the information you're looking for through the Report Writer and then embed this report as a Report Resource on the Application Details page.
Thanks. Do you think I will need to grab it from the APM_ComponentTemplateSetting table and do some kind of 'INNER JOIN'? Or is there a variable available? SQL 'Finaglers' are you out there? ;)
1 of 1 people found this helpful
The information is stored in the APM_ApplicationTemplateSetting table or the APM_ApplicationSetting if overridden.
It’s stored in a format of key/value pairs.
I am having problem with an INNER JOIN query using your suggestion. I want to harvest the Frequency and Timeout from the Key column in the APM_ApplicationTemplateSetting table and then match it to the APM applications in the APM_Application table. Can you or anyone help?
The DB Manager doesn't like this query:
INNER JOIN APM_ApplicationTemplateSetting
ON APM_Application.TemplateID = APM_ApplicationTemplateSetting.ApplicationTemplateID
APM_ApplicationTemplateSetting.Key="_Frequency" AND APM_ApplicationTemplateSetting.Key="_Timeout"
It is stating " Incorrect Syntax near the keyword 'Key' "
I have narrowed it down to this phrase: APM_ApplicationTemplateSetting.Key="_Frequency" I think!
I appreciate any help.
"Key" is one of reserved keywords in SQL so it needs to be surrounded with brackets when it is meant as column name, so you need to replace all ".Key" by ".[Key]" in your query.
Thank you very much, Petr!
I also removed the 'WHERE' and everything below it to produce the results.
I want to harvest the Frequency and Timeout from the Key column in the APM_ApplicationTemplateSetting table and then match it to the APM applications in the APM_Application table.
You need to include APM_ApplicationSetting table because these parameters inherited from template can be overridden on application level. In addition to this default values (300, 300) are used when they are not specified in any of those two levels:
ISNULL(ISNULL(asFreq.Value, atsFreq.Value),300) as Frequency,
ISNULL(ISNULL(asTimeout.Value, atsTimeout.Value),300) as [Timeout]
LEFT JOIN APM_ApplicationTemplateSetting atsFreq ON APM_Application.TemplateID = atsFreq.ApplicationTemplateID AND atsFreq.[Key]='__Frequency'
LEFT JOIN APM_ApplicationTemplateSetting atsTimeout ON APM_Application.TemplateID = atsTimeout.ApplicationTemplateID AND atsTimeout.[Key]='__Timeout'
LEFT JOIN APM_ApplicationSetting asFreq ON APM_Application.ID = asFreq.ApplicationID AND asFreq.[Key]='__Frequency'
LEFT JOIN APM_ApplicationSetting asTimeout ON APM_Application.ID = asTimeout.ApplicationID AND asTimeout.[Key]='__Timeout'
I've taken the liberty of putting Petr.Vilem's hard work above into an Orion Report Writer report which can be downloaded at the link below.