Hi @Dawid.Wrobel, I found these pieces of content that could help https://docs.appdynamics.com/appd/onprem/latest/en/events-service-deployment https://community.appdynamics.com/t5/forums/searchpage/tab/message?filter=location&q=%22event%20service%22&noSynonym=false&inactive=false&location=tkb-board:knowledge-base&page=2&collapse_discussion=true ... View more

Hello David in General, AppDynamics Different components uses MySQL Databases , not centralized but with each component (each controller has it's MySQL database, enterprise console has its database, EUM too, etc.)  check the bundled Database Controller Component Versions (appdynamics.com) you don't have to be super MySQL admin, but mandatory to write down the admin user and password 🙂 as support will need it for any support issues, also you will find here how to backup and restore the bundled Database Controller Data Backup and Restore (appdynamics.com) Database agent is the agent that monitor different Databases. that you application work with. remotely connected to these Databases through JDBC connection, and run queries to get the performance data about each , you can find here the supportability matrix Database Visibility Supported Environments (appdynamics.com) BR ... View more

@Dawid.Wrobel  Correct...AppDynamics, by default, will create a snapshot every 10 minutes, and they capture a 10-second window unless they are in what is called a diagnostic session.  The UI can be used as you mentioned to change the frequency, but I must have misunderstood your question. I assumed you wanted to change the time period for what is captured...rather than the frequency.  If you feel there is a need to take more frequent snapshots, I would ask what that reason is, and from my experiences, that change happens when there are systemic issues happening and the default rules don't do a good enough job capturing what is needed for troubleshooting, therefore, I suggest creating a manual diagnostic session rather than changing those types of global settings.  If no paper icon is available, meaning, there is no partial or full call graph, it just means a snapshot was created without there being a slow, very slow, or error that will put the transaction into a diagnostic session. It can almost be considered normal operations or behavior. Call graphs, whether they are partial or full, generate due to a diagnostic session. AppD can create the diagnostic session or you can manually. If you look at the differences, you will see a partial call graph does get to the line causing a violation, but will not encompass the entire flow like when having a full call graph...which is very useful if you want to know what is effected or being caused by downstream or upstream transactions. If a transaction happens that deviates from a normal activity during the snapshot being captured, AppD will start a diagnostic session which will capture the method calls seen in a call graph. Depending on when that diagnostic session started, you may/may not get the whole transaction flow. If nothing deviates from what AppD thinks is normal, then there would be no reason a diagnostic session gets created, meaning a call graph wont be generated and that is when we wont see a paper icon. You can initiate a diagnostic session manually or via rules which will give you the control to capture when, for how long and how many snapshots per minute you want...which will surely get you the details you need.   I am happy to try and help some more if you have further questions.  ... View more