AppFirst Transactions unlocks the quick and real time information on live data as it’s happening between applications.
What is AppFirst Transactions?
Transactions will allow the user to experience real time data by showing end to end transaction visibility from the data AppFirst collects. This tool shows process topology, transaction timeline, and summary data for multiple types of transactions. You can select one of three types of transactions to start your trace from:
Database transactions: Trace a transaction “backwards” starting from a database server’s SQL statements back to the web request
Web Server transactions: Transactions can be traced directly from web requests in the form of URL
Process transactions: Transactions can be started from any point in the trace
The Linux collector version 112 is now available.
Notable improvements include:
- Fixed rare interaction with garbage collection in go processes
- Added logging of encrypted oracle processes
The Linux collector version 111 is now available. Notable improvements include:
- Resolved issue where go processes caused the collector process to terminate.
- Improved filtering of apache transaction log output.
With the recent release of the Linux Collector version 108 we have isolated a bug with 32-bit applications on 64-bit servers. We have released a new version 109 of the Collector which updating to will resolve the bug of 32-bit applications on 64-bit servers.
For any customers that have already updated to v108 it is recommended to update to v109 ASAP.
Updating the Collector can be done in the user interface under Admin -> Collectors and or can be found how to manually do so in the Getting Started document.
The Linux collector version 108 is now available. Notable improvements include:
- Transactions bug fixes
- Preserve proxy file on upgrade in deb package
AppFirst now supports Warden container technology, which is used in CloudFoundry. Warden provides a service for managing a collection of containers and defines a protocol for clients to send requests to and receive responses from the server.
Warden containers make use of Linux cgroups. As such, many of the processes executing in a container are isolated from processes running in other containers as well as processes running in the underlying OS, outside of any cgroup context. This creates a scenario where details describing the application components running in the context of a container should be accessed from within the container context as opposed to from outside the container context in the underlying OS. This means that an AppFirst collector should be able to be installed in both the underlying OS and within each Warden container.
AppFirst support of CloudFoundry results in collectors installed using Bosh that provide details of the CloudFoundry system and servers. This install occurs when a CloudFoundry instance deploys servers. No user interaction should be required.
Examples are offered in the AppFirst support docs to describe how to install the collector in a Warden container. Collector and Warden containers
The Windows collector version 71 is now available. Notable improvements include:
- Stability improvements for the AppAccess Service.
- Fixed an issue that could show up at installation time if network connectivity is not available during the startup process.
- If there are issues at startup, the collector will exit and generate an Event Log explaining the problem.
- Handling of a random problem that could disable log collection.
- Improved statistics when using overlapped sockets.
- Event Log collection will include the Event ID.
This is a reminder that we will be shutting off API versions 3 & 4 on Monday, March 16, 2015 and will now be required to use our API version 5.
All documents can be found at http://support.appfirst.com/apis/ for any assistance that may be needed in setting up API version 5.
If you have any questions at all, please email email@example.com.