Original Author: Dan Breslin
Dynatrace >= 5.5
Although dynaTrace also supports Guidewire Policy Center and Billing Center, this fastpack is limited to Claim Center.
August 2013 Initial Release
October 2013 - Additional Business Transactions for Username and Event Source
1 System Profile 1 Plugin 2 Dashboards
Latest Release from GitHub
The following components are part of this FastPack:
The reference Guidewire System Profile contains a set of basic metrics required by the Dashboards of this FastPack for Guidewire Claim Center.
The Guidewire Dashboard gives insight into the Claim Center Overall Performance and Buisiness Transaction volume and response times.
The Guidewire JVM Dashboard gives insight into health and performance of the Claim Center Java Virtual Machne
Feel free to contribute any changes on Github
Is it just me, or is this fastpack not listed on the main page?
thanks for letting us know - its now showing up. The labels were not set on that page
Hi Andreas, It seems the link for the documentation (FastPack Documentation (German).pdf) is for Oracle Weblogic in german and not for the GuideWire plugIn.
You are correct. I think this was a copy/paste error from a different fastpack page. I removed this misleading information
Hi try to install the plug in on our Dynatrace server 5.6. It install properly without error messages but it does not show up in the list after.
Is this version of plugin compatible with 5.6 ?
Hi. This FastPack contains a System Profile, a Monitor and 2 Dashboards. You will not see the FastPack showing up in the list of installed plugins - BUT - you should see a new System Profile on your dynaTrace Server which also has a Monitor Configured. Additonally you should see two new Dashboards on your dynaTrace Server.
FastPacks "look like" plugins - but they are treated slightly different. You wiill not see them in the list of installed Plugins. what happens during installation of a FastPack is that the contained Resources (Sys Profile, ....) will be added to your dynaTrace Server. You can then - if you want to - delete these resources again if you dont need them any longer
Hello,I have installed the Guidewire fastpack for one of our customer. However, our customer does already have an existing System Profile that is connected to their Guidewire Java Agent. The "Guidewire" System Profile does have some "metrics" that need to be transferred to our System Profile. I have looked into the Guidewire System Profile and I identified the following Measures, BTs and Sensors that presumably need to be transferred. See screenshot: Guidewire_system_profile_necessary_metrics.jpg
Now, I would like to check if that is it? Or if I am missing something that need to be copied over from the "Guidewire" System Profile?
When using the Guidewire plugin from version 2 of the fastpack, what permissions does the plugin need on the DB server to retrieve the stats required to populate the DB performance dashboard? Our DBAs are not willing to provide full sysadmin access so need to know the specific requirements.
Please, do you know if this is compatible with dynatrace 6.2?
When I try to install it as a plugin, I got an error message: "the bundle guidewire... is invalid" or should I use another way to install it?
I don't see any new system profile created.
I have the same issue. The problem seems to be with the System Profile, I tried to import the XML file and it returned an error.
Hi all, I just took a look at this. I don't maintain this fastpack or have any other working knowledge of it, but the fastpack itself appears to be missing the required manifest file and the plugin.xml file was missing some data. I've updated it, but if you encounter this again, you can always change the .dtp extension to .zip, unzip it and manually import the profile and dashboards.
Does anybody know what the TS value is in the fastpack? It is configured as a measure and a BT and I am looking for a unique value to use as a BT filter. My client wants to define two stages of a wizard as different transactions but both have the same user action (click next) and the same eventSource (FNOLWizard:Next_act) so I'm looking for something else to use to differentiate them
I just looked in the system profile. TS is Web Request Parameter Value. Dynatrace is capturing the value of the request parameter ts with a measure and processing it in a BT. The BT is simply looking for server side purepaths that contain the ts request parameter and splitting on that value.