![]() You might be worried about configuring how much data to hold in memory (this was a common problem in PingPlotter 4 as more targets were added). Now we know that data is being saved automatically, and you can open it, export it, and delete it from the session browser. If we're running PingPlotter as a Windows service, then we'd need to restart the service (or restart the machine) to store the changes. If we specify a different location to store the file, we'll want to make sure to close and relaunch the program to get the changes to take effect. There is an option in the Auto-Save to change the default location of the sessions.ppdata file. If we're running the program as an application, then the file's default location is in our user application data folder C:\Users\**username**\AppData\Roaming where **username** is the username of the currently logged in user. If we're running PingPlotter as a Windows service the file's default location is in the C:\ProgramData\PingPlotter 5\ folder. These will eventually be deleted.Īll of the data in PingPlotter is saved to a file titled "sessions.ppdata" in one of two locations. Will Delete - any inactive trace sessions that haven't been set to save.Archived - any inactive trace sessions that have been saved and are closed.Pause - any trace sessions that are open in PingPlotter now, but are paused.Active - any trace sessions that are actively collecting data.There are four different persistence types in the session browser: The previous trace sessions can be found in PingPlotter by going to "File" -> "Manage Sessions." From the session browser, we have the options to reopen or delete a previous session, as well as the option to export a session (which will save off a. Once you've collected data but you've closed it, how do you reopen it (or delete it, or export it, or continue tracing)? The tab's "close" icon will show an "X" to indicate that this data will be discarded on close, and a checkmark to show that it will be kept. Here we have options to "Discard on close," or "Keep (auto-save)." To do this, open a trace window (if it's not already open, use the "All Targets" summary to find it, then open from there), and right click on the target tab. If you're collecting data from a target and you decide you want to keep it (and you're in a mode where it's not yet marked to keep), you can switch to "Keep" mode (or discard mode) manually at any time. This is a great option if you have a handful of long-term targets that you always want to collect from, but you want to occasionally mix in some targets that you don't want to stick around. "Only when selected" - this will result in PingPlotter auto-saving data, but marking it to discard when you close. ![]() "After:" - this setting will only keep sessions that have met or exceeded the timeframe that is entered.If you start tracing a target and stop after 3 samples, that "session" will get marked to keep. "Always" - this will keep every target's data in PingPlotter's datastore.There are a few different options for how to recognize a session as one you want to keep around, or one you want to throw away when done. The auto save settings can be configured in PingPlotter by going to either "Edit" -> "Options" -> "Auto-Save" (on Windows) or "PingPlotter" -> "Preferences" -> "Auto-save" (on Mac). Configuring the definition of "short term" sessions This behavior is a direct result of feedback from our users (and us) that prompting to save on close was frustrating. If you closed a session you really wanted to continue, you can reopen that session within 5 stop/restarts and continue. When a session is marked for deletion, it will be fully deleted after you close and reopen PingPlotter five times. Short term sessions are saved continuously, but if you don't collect data long enough, they are marked for deletion when closed. Closing and restarting will resume those sessions. Long-term sessions (a session is a set of collected data from a trace to a target) are saved continuously, and when you scroll back in history, the data is retrieved from disk. This helps make sure that none of your data is lost at any point (for instance - if there is an unexpected restart, a power failure, or any other event that would put data data at risk). PingPlotter 5 writes all data in real-time to its local data store. In PingPlotter 5, it should "just work", saving what you want, discarding what you don't (if you show it what kind of stuff you don't want). This is something that shouldn't happen to you in V5. In V4, it didn't save automatically, and sometimes important data wasn't available when you needed it (unless you did some configuration that didn't always think the way you do).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |