BookmarkSubscribeRSS Feed
Grumbler
Obsidian | Level 7

hello, just wondering if APM captures information when a particular enterprise guide project or dashboard is executed.

it's rather difficult by looking at the artifactresult table from the apm.

it seems to capture steps within the enterprise guide, but we just want to see the information about the whole project, not broken down into pieces.

thanks.

5 REPLIES 5
LinusH
Tourmaline | Level 20

What version are you using?

If you are using a quite recent release you could might look at using Environment Manager, that hos some out-of-the box reports/tools.

Data never sleeps
Grumbler
Obsidian | Level 7

we are using the newest version.  the pre-built nightly reports offer some useful information but doesn't cover everything though.

jakarman
Barite | Level 11

APM is having some adjustments to the arm logging and having some sample reports.  The event manager is an extension evolution on that. Still sample reports and adding a DBMS postgres for collecting data. The collecting of data of SAS is still ARM. SAS(R) 9.4 Logging: Configuration and Programming Reference, Second Edition 
- Why postgres? It are things inherited form other parties where SAS did some imbedding of that.

- Why sample reports? They are nice to show easy to implement. The disadvantage not covering all possible questions.
This is the area where SPLUNK as bi-tool is often found to analyse logfiles and do reporting on (SOC center and performance/tuning).

ARM doesn't capture things in Eguide it captures things in the SAS processing (server side).
Having all that information in arm files you can build any report as you like, only the time needed to do that is a limitation. 

---->-- ja karman --<-----
Grumbler
Obsidian | Level 7

right, it captures server side things.  it's difficult for us to group a bunch of things into one item that we are looking for as far as performance measurement.

SASKiwi
PROC Star

So far as I understand EG projects are only known within EG itself and what gets passed to the SAS Servers is simply SAS code. SAS servers are not "EG project aware".

If there is a need to closely monitor individual EG projects then exporting these to run as SAS server batch jobs is one obvious solution.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 5 replies
  • 1372 views
  • 0 likes
  • 4 in conversation