Questions? Here are the answers!

Where does Retrospective come from?

Retrospective emerged from our daily work with log data, including challenging tasks in the domain of DevOps and production support.

How does Retrospective collect log data from files?

Local log files on your machine are directly accessed via the file system. Log files on remote hosts are fetched over SSH using standard Unix/Linux commands like grep, awk, sed, etc. Retrospective applies search arguments on the remote hosts in order to limit the data sent over the wire.

How does it work for Docker containers and Kubernetes?

Retrospective uses the "docker" and "kubectl" commands to fetch log data from containers that write to the standard output stream. These tools must be installed and properly configured on your machine. Both searching and monitoring is possible. Naturally the monitoring function is the primary use case for container logs because usually there are only a couple of megabytes of log kept back by Docker or Kubernetes.

What is the difference between "Search" and "Monitor"?

The "Search" function filters and fetches existing log data from files or containers. The "Monitor" function filters and fetches log data as it is produced (similar to the "tail" Unix/Linux command). Both functions filter the data with user-defined search criteria. When searching or monitoring log data from files on remote SSH servers, only the filtered data is transferred to the local computer.

Can I mix different sources of log data in Retrospective?

Yes, for example consider monitoring log files from batch processes that send events to Kubernetes pods. You can have a Retrospective profile that merges data from remote log files with the logs from Kubernetes pods in a single, unified view.

How does Retrospective deal with big volumes of log data?

When the collected log data kept in memory exceeds a certain limit, Retrospective writes excess data to disk storage. When the data is needed (i.e. when you’re viewing a different chunk of log data), the information is read back from disk. All this happens in a transparent way in the background through a set of options. The user is granted full control over Retrospective’s memory and disk storage usage.

Why should I use Retrospective instead of a complex log collecting/indexing infrastructure?

The most common uses cases we have seen for Retrospective are: 1. You need ad-hoc capabilities for log search and monitoring without fuss. No installation of log collecting agents, index databases and server components is required for Retrospective. 2. Results are available immediately in Retrospective, without the time delay of central data collection. 3. Retrospective can help you during software development by providing log data merging and structuring capability when running local tests with multiple containers, Kubernetes or Docker Swarm development setups, and log files. 4. Sometimes not all or not enough volume of log data is collected and indexed in an existing log management infrastructure. It may be that you are the only person who needs those logs, or the log ingestion is too expensive volume pricing). There are cases where log collection and indexing is not always feasible IoT (Internet of Things) or embedded computing. 5. Retrospective offers a quality desktop windowing environment using the native GUI widgets of your machine that is highly configurable and works well on multiple high-res monitors. 6. Grokking log data is a good reason to justify buying a new high-end laptop.

How can I structure log data with Retrospective to leverage the information?

Retrospective analyses log data and proposes detected name/value pairs in order to show them in dedicated columns of the result table. You can use those automatic definitions or create your own detection criteria based on split characters or Regex patterns. Retrospective also lets you use existing log level definitions and create new ones. Every such definition specifies how individual log entries shall be interpreted by Retrospective in order to find/extract the appropriate log level. It also contains information on how log entries with an assigned log level shall be displayed in the result table.

What is "Result Highlighting"?

Result Highlighting means emphasizing specific elements in the log data by using different colors. Retrospective automatically highlights texts based on predefined highlighting sets for currency, date/time patterns, name/value pairs and others. Additionally you can define highlighting criteria on the fly or define your own persistent sets that can be reused at any time later.

What more can I do with log data that was collected and structured in Retrospective?

Retrospective features local filtering and columns manipulation, JSON/XML formatting and context diving. The data can be exported to text, csv or Excel files. We are interested in learning about other possible export capabilities or integrations, if you have an interesting use case then please drop us a line.

Do I need to install a JRE first?

If you download Retrospective with a bundled JRE (Java Runtime Environment) then you don’t have to worry about this. If you download Retrospective without a bundled JRE, then please make sure that you have a suitable JRE installed on your computer by entering "java -version" in a command window. The java version should be the same as (or newer than) the version indicated on our website. We recommend using the Retrospective version with a bundled JRE.

How does your upgrade policy work?

You get one year's worth of upgrades (functionality and bug fixes) for free with your first year's subscription. After that, you can continue the upgrade program with a discounted price.

I have a problem, it's not working how I think it should. What do I do?

Send us a bug report together with your license key.

What is your product roadmap?

We want to make Retrospective the best software product for personal log data grokking and were keen to implement new features that add value to Retrospective. If there's something you'd really like, let us know, and we'll take a look at it.

Is there a 32 bit version of Retrospective?

We assumed all Mac fans would have junked their old pre-2006 Macs by now and therefore we do not provide a 32-bit Mac version. Furthermore we are planning to remove the support of 32-bit versions for Windows and Linux in the near future.

Can I run multiple versions?

You can install different versions by using different directories. However, you cannot run the Retrospective instances simultaneously.

Does Retrospective support non-english character encodings?

Yes, Retrospective supports pretty much all character encodings that exist on the planet. In most cases, the correct encoding is automatically detected.

Security policy at our company requires password change every two months. Do I have to change user credentials on each host definition?

Retrospective enables batch editing hosts definitions. Simply select desired hosts definitions and change authentication information on all of them at once.

I need to search logs on servers I access with PuTTY on a daily basis. Can Retrospective help me with that?

Retrospective can import hosts definitions from PuTTY. The passwords are not imported automatically. Retrospective has an SSH console built in, so you can stay in one environment for your work.

I can only login to remote servers by: client certificates / sudoing / using jump hosts, can I fetch log data from these servers with Retrospective?

Yes, Retrospective allows client certificates, several sudo and su combinations and the use of SSH jump hosts.

How can I select Kubernetes pods for collecting log data?

There is support for selecting pods by labels with most of the Kubernetes selectors like "equals", "in", "not in", etc.

What can I avoid to miss critical log entries?

Retrospective features search results highlighting based on log entry severity (CRITICAL, WARNING, INFO) or on user defined terms. Therefore it's hard to miss important information.

How does Retrospective optimize the search process?

Retrospective analyses a small amount of log data from the beginning and the end of a file. The analyzed information lets the program find out whether individual files contain data that is located within the time period specified in the time search criteria. All files with log entry dates outside of this period are excluded from the search process.

I tend to make the same searches on a regular basis, can I store the search parameters somehow, so I don't have to define search filter each and every time?

Retrospective features search definitions bookmarking, allowing to store given search parameters and execute them later with a single click. Additionally, a layout of multiple result windows on multiple high-resolution monitors can be saved as a Retrospective view and later be restored.

Any other questions?

Contact Us