Hello,

I'm able to reproduce the behavior with emergency mode requiring you to enter the emergency mode user/pass to shut down. You are certainly welcome to reach out to the WRC to confirm if this is intended behavior, but I suspect that it is. I am wondering what the use case is here as emergency access mode is a special mode, intended for use "under certain dire circumstances, such as if there is severe damage to security configuration information or if no users with the %Admin_Manage:Use or %Admin_Security:Use privileges are available". In those situations you would be taking manual steps so uninteractive shut down would not be necessary.

Could you simply use a normal login and not emergency mode?

The other commenters have good suggestions but I would recommend additionally collecting a pButtons to compare. Try and determine if there are any differences other than OS - hardware, memory configuration, global mappings, or anything else. We want to make sure we're comparing apples to apples! If everything seems to be the same, then you could reach out to the WRC who can help investigate this further.

As far as I know I don't think this behavior has changed in 2020. While I was testing the monitor myself recently I noticed the dropdowns getting cleared but when I saw that auto-refresh was disabled in newer versions I didn't  think I needed to follow up on this. If you disable the refresh global you'll find that the tagline of 60s refresh no longer appears as well.

If you really felt this was worth changing I'd recommend that you reach out to your ISC representative (or the WRC) but I would be prepared for the response that the monitor is not intended to be a complete solution. That is not to say that a change to help alleviate the behavior are seeing would not be considered, so if this is really tripping you up it would be worth reporting - maybe others have the same pain and there's enough momentum to get this addressed.

You may find the following article useful in terms of building your own monitoring solution.

https://community.intersystems.com/post/monitoring-intersystems-iris-using-built-rest-api

Hope that helps.

Hello Julian,

The default behavior in your version would be for the activity monitor page to not auto-refresh, but I saw in one of your posts that you have enabled SMP auto-refresh.

https://community.intersystems.com/post/queues-refresh-iris-20191

The activity monitor dashboard is really just a starting point - once you start collecting data using the activity monitor you can easily access the monitor tables such as ens_activity_data.days with SQL.

Hi Julian,

You could do this with a custom Ensemble utility function but from your description I think parenthesis syntax should work just fine.

Defining Custom Utility Functions

Parenthesis () Syntax

HL7.(PIDgrpgrp(1).ORCgrp().OBR:UniversalServiceIdentifier.identifier) should return a concatenated string from looping through the ORCgrps - you could then search that string to find the value you are looking for.

Hope that helps!

Hi Michael,

I assume you were looking at the %Library.File documentation for FileListFetch. FileListFetch is not meant to be used directly, but is a part of a class query which can be used as documented here:

Defining and Using Class Queries

https://cedocs.intersystems.com/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25Library.File

If you can navigate to the directory then you could use ##class(%Library.File).GetFileSize(), however for a remote FTP server this probably wouldn't work. You would want to use %Net.SSH.SFTP as documented here:

Using SSH

https://cedocs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?APP=1&CLASSNAME=%25Net.SSH.SFTP

edit: the FileList query is not in %Library.File - I am not sure where that query comes from but the rest of my post remains revelant