Ask the Expert - Admin Studio with Lukasz Karnasiewicz
Join Lukasz Karnasiewicz (karnl) in this Ask the Expert session (7-11 Oct) on Admin Studio!
About Lukasz: Lukasz Karnasiewicz has 15 years of experience in the IT industry. He joined Pega 6 years ago through the Antenna acquisition where he worked for 5 years as a Software Engineer and Manager. At Pega he manages the Core Engine Performance team and is a Product Owner responsible for platform observability and operations tools. He is passionate about improving everything (especially software performance) as well as helping customers accomplish their goals and fulfill their needs using the software that Pega builds.
Message from Lukasz: Hi All! I look forward to all your questions regarding Admin Studio and I hope to be able to get a lot of your feedback about it from this session. Specifically, I would like to learn how Admin Studio is helping you with system administration and day to day operations and how we can make it better.
Hello Lukasz, it's a great opportunity to ask you a question in this session. I like the new Admin studio very much. My question: Is there a possibility to postpone agent start as it was in SMA?
I have a use case where I need to trace exactly the first run of the agent. If the agent is stopped or failed I need to start it first. Then the screen with agent list refreshes and I need to scroll to or filter out the agent I'm interested in. Only then I can select it and trace next run (or trace now if it's on a specific node). But at that moment it's tracing not the first run of the agent, but the second one (in best scenario).
Thanks for the questions. It's great to hear that you like the new Admin Studio.
Indeed the agent tracing feature in Admin Studio is currently limited to agents that are enabled and whose execution will start within next 30 minutes. I've added a User Story to address this in future Pega releases.
What you could potentially do be able to trace this agent is to temporarily modify the agent definition (activity) and introduce a short delay of 1-2 mins at the begining so that you're able to trigger the tracing from within Admin Studio.
How is Admin Studio used in conjunction with PDC and other cloud tools?
Also, if a client is trouble shooting, trying to understand alerts happening at the node level, how do they troubleshoot. Is there additional documentation or training I can refer them to?
For example, I have a new client using the following dashboard. They have no idea where to start when troubleshooting or remediating the identified issues. How should I instruct them to act Utilizing Admin studio?
Admin Studio and PDC serve a bit of a different purpose. First is used to oversee, troubleshoot and manage a system and second is used to monitor it (both from performance and functionality perspective), gives you recommendations on how system's performance can be improved but doesn't (yet) let you perform any actions. You could use them in conjunction in many different ways depending on the situation. For example if one of your agents stopped working, Pega would send an alert to PDC which would notify you via email (if you have the notifications configured). The next steps would greatly depend on the underlying root cause but in our example you would then log into the Admin Studio and restart that agent.
When it comes to other cloud tools, recently we've integrated some of the Admin Studio capabilities into Pega's Global Operations Console so now our GCS and SRT Engineers can troubleshoot Pega Cloud issues more easily.
Understanding and troubleshooting alerts can be difficult and varies greatly depending on the alert. There are couple general places where you could start learning about it: