## Sessions Overview |

| The information required to start a profiling run is called a session. Sessions are saved in the file `{User home directory}/.jprofiler6/config.xml` and can be easily migrated to a different computer by importing this file in the setup wizard. When upgrading JProfiler, your settings of older installations are imported automatically.

| Sessions are created on the "New Session" tab of JProfiler's start center. by selecting Session->New session from JProfiler's main menu. automatically by JProfiler's application server integration wizard. by importing them. from en external config file. Sessions are edited, deleted and opened in JProfiler's start center. through the open session dialog which is accessible from JProfiler's main menu via Session->Open session.

| The session settings dialog can be invoked from the open session dialog or the start center. the the session startup dialog that is displayed just before a session is started. JProfiler's main menu and the toolbar. The toolbar button and the menu item Session->Session settings open the session settings dialog.

| The session settings dialog is divided into 4 sections: Application settings The application settings section collects all information that is required to start your application with profiling enabled or to connect to a running JVM that has already been started with profiling enabled. If you use an IDE integration, this information will be provided by the IDE. Filter settings In the filter settings section, you define which classes should be considered when recording call-stack information. Defining appropriate filters will help you to reduce data overload and minimizing CPU profiling overhead. By default, JProfiler adds an exclusion list Profiling settings In the profiling settings section you can configure the way your application is profiled and change the focus of a profiling run toward performance or accuracy, CPU or memory profiling. Trigger settings In the trigger settings section you can optionally define a list of triggers. With triggers, you can tell the profiling agent to execute specific actions when certain events occur in the JVM. The actions are also executed during offline profiling.

| If you change filter, profiling or trigger settings for an active session, the new settings can be applied immediately if you profile a 1.6+ JRE. Apart from telemetry data, all recorded data including the heap dump in the heap walker will be discarded in that case. When profiling settings are updated, a bookmark will be added to views with a time-line, such as the telemetry views. The application of the new profiling settings may take some time, especially if filter settings are changed and the method call recording type is set to dynamic instrumentation. In this case, changes in the instrumentation requires that classes have to be retransformed to reflect the new filter settings. If you profile a pre-1.6 JRE, you have to restart the session. View settings on the other hand, are always adjustable during a running session and are saved separately for each session.