FirstSpirit Quick Start Guide – SaaS Customer Logging

This document provides a concise, non-exhaustive overview intended to help you efficiently leverage our SaaS customer logging capabilities.

Scope and Purpose

• Aim: Offer practical tips to optimize the use of our SaaS customer logging.
• This guide is not exhaustive; it covers essential steps and commonly used logs.

Logging Environment

In your logging environment, you will have access to logs for the three instances:

• Development (Dev)
• Quality Assurance (QA)
• Production (Prod)

Available Logs

The following log files are accessible:

• fs-server.log
• catalina.out
• fs-wrapper.log
• fs-clients.log

Access and URL

Logs are available at:

https://customername-logging.e-spirit.hosting

Note: Replace the string customername with your technical customer name. The technical customer name corresponds to the name assigned to your FirstSpirit instances.

Example

If your technical customer name is acme-corp, the URL would be:

https://acme-corp-logging.e-spirit.hosting

Getting Started

1. Log in using your cloud credentials.
2. Navigate to the Discover area to begin exploring the logs.

Filtering and View Configuration

On the left side, you will see a set of fields that can be used to filter the log view. Key fields include:

Besides the message field, you usually click on the name instead of the right-side plus to see the filter recommendations.  

• message: This field is particularly useful for filtering by log message content.
  • Recommendation: Hover your mouse over this field and click the right-side plus icon that appears. This action switches the view to display the actual log lines in the list instead of the document structure.

Note: Using the message field to filter helps you quickly pinpoint relevant log entries in the current view.

• host.name: This field allows restricting results to a specific instance. The internal instance name is used.
  • Example: Customername-prod.intern.hosting
  • Important: Unlike the public instance name, you must include the -prod suffix here.
• fields.severity: Limits log levels. Allowed values: INFO, WARNING, ERROR.
• Log.file.path: Filters for which log files to view. By default, all files with entries are shown in the view.

General Tips and Notes

• The system always shows up to the latest 500 entries. If your search yields more than 500 results, narrow the search accordingly.
• This limit also affects the suggestions in the left-side fields; if the first 500 entries do not contain catalina.out, it will not appear in suggestions.
• You can adjust this via time ranges or by applying filters that exclude certain elements.

• Add Filter is useful for searching for or excluding specific terms. For example, to filter out all messages containing the word smartsearch, add a filter for that term.

  

• If you need to exclude a specific class, specify the entire class name.
• Very long stack traces may not display in full. You can expand the log line by clicking the “>” to open the line, scroll down to the message, and then expand to reveal the full stack trace.