Software-Telemetry

Using the Fabasoft app.telemetry integration possibilities, as described in chapter Fabasoft app.telemetry Integration (SDK), applications can provide log, trace and/or debug information to Fabasoft app.telemetry.

Fabasoft app.telemetry can be used to follow and analyze single requests through a complex and heterogeneous infrastructure of those integrated applications.

Online Software-Telemetry Logs

Fabasoft app.telemetry can be configured to display requests received from applications using the Fabasoft app.telemetry integration. Each request is displayed as a single line together with general information like start time, duration or the Fabasoft app.telemetry agent that received the request first.

Software-Telemetry Sessions

Explicit Software-Telemetry session

Fabasoft app.telemetry provides a list of applications available for an explicit Software-Telemetry session in the “Start Software-Telemetry Session” dialog window. An explicit Software-Telemetry session can be started by selecting the appropriate application, choosing one of the filter values provided by the application, selecting one of the supported recording levels (standard, detail or debug), specifying a session description and a duration for which the session is running.

An explicit Software-Telemetry session can by stopped using the “Stop Software-Telemetry Session” dialog window. After a Software-Telemetry session has been stopped, all available Software-Telemetry data is automatically transferred from the Fabasoft app.telemetry agents to the Fabasoft app.telemetry server where the data is processed and stored as session. The Software-Telemetry session can then be loaded in the Fabasoft app.telemetry client, by whereby the session is prepared by the webserver and graphically displayed in the client.

An active Software-Telemetry session has impact on the analyzed systems. The impact depends e.g. on the selected recording level, the filter selectivity or the information passed by the instrumented applications.

Implicit Software-Telemetry session

Fabasoft app.telemetry can be configured to collect Software-Telemetry data permanently (without explicit start and stop) for selected applications. Active permanent Software-Telemetry collection has impact on the analyzed systems. The impact depends e.g. on the selected recording level or the information passed by the instrumented applications.

Analyzing a Software-Telemetry session

Stopped explicit Software-Telemetry sessions can be easily loaded and analyzed with the app.telemetry client as already described above.

Software-Telemetry data received from implicit Software-Telemetry sessions can be analyzed by selecting the appropriate request from the Online Software-Telemetry Logs.

Software-Telemetry data received from automatic Software-Telemetry sessions (as described in chapter Automatic Software-Telemetry Session) can be analyzed by selecting the appropriate request from the Software-Telemetry session.

Persistent Software-Telemetry Logs

Fabasoft app.telemetry can be configured to store all requests received from applications using the Fabasoft app.telemetry integration in a relational database. The relational databases are not part of Fabasoft app.telemetry. Each request is stored together with general information like start time, duration or the Fabasoft app.telemetry agent that received the request first. Supported relational databases are described in chapter Supported Database Systems.

Software-Telemetry Log Analysis

Fabasoft app.telemetry can be configured to prepare all requests received from applications using the Fabasoft app.telemetry integration for analysis. Within this configuration, application specific Software-Telemetry log columns can be defined that are used for the computation of aggregations like number of requests, total request time or average request time. Computed values can be displayed grouped by one of the defined columns. Based on that computation, Fabasoft app.telemetry allows the selection of a column value as a filter and an additional grouping by other corresponding columns (drill down).

Requirements for Software-Telemetry log analysis are persistent Software-Telemetry logs and a relational database for storing aggregated values. The relational databases are not part of Fabasoft app.telemetry. Supported relational databases are described in chapter Supported Database Systems.

Service Desk Integration

Fabasoft app.telemetry can be configured to send selected requests or a selected Software-Telemetry session to the Fabasoft Support service desk. This configuration requires access to the Fabasoft Support service desk based on a Fabasoft Support agreement. A Fabasoft Support agreement is not part of Fabasoft app.telemetry.

Syslog Integration Module

Fabasoft app.telemetry can be configured to capture Linux syslog entries as Software-Telemetry requests in a Software-Telemetry log pool. This configuration requires a Fabasoft app.telemetry agent as well as the Fabasoft app.telemetry Syslog Forwarder module to be installed on the target system. For a list of supported platforms see chapter Fabasoft app.telemetry Integration for Syslog.

Telemetry Raw Data Inspection

Since Version 2014 Fall Release Fabasoft app.telemetry provides a specific view to analyze the telemetry raw data collected from instrumented applications. Specify the reporting time range and the resolution and you can start analyzing the telemetry data, but be careful the data processing may have an impact on the server load especially when using a long time range, a small resolution or when working on a big data set with massive telemetry data.