From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* camel_srt.c
|
|
|
|
* camel Service Response Time statistics for Wireshark
|
|
|
|
* Copyright 2006 Florent Drouin (based on h225_ras_srt.c from Lars Roland)
|
|
|
|
*
|
|
|
|
* Wireshark - Network traffic analyzer
|
|
|
|
* By Gerald Combs <gerald@wireshark.org>
|
|
|
|
* Copyright 1998 Gerald Combs
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU General Public License
|
|
|
|
* as published by the Free Software Foundation; either version 2
|
|
|
|
* of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
2012-06-28 22:56:06 +00:00
|
|
|
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
|
|
|
|
2012-09-20 01:48:30 +00:00
|
|
|
#include "config.h"
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
#include <string.h>
|
|
|
|
#include <gtk/gtk.h>
|
|
|
|
|
2008-04-13 00:55:59 +00:00
|
|
|
#include <epan/packet_info.h>
|
|
|
|
#include <epan/value_string.h>
|
|
|
|
#include <epan/tap.h>
|
|
|
|
#include <epan/packet.h>
|
2013-12-30 22:07:38 +00:00
|
|
|
#include <epan/dissectors/packet-camel.h>
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
|
2012-01-16 01:07:52 +00:00
|
|
|
#include "ui/simple_dialog.h"
|
|
|
|
|
2012-01-15 21:59:11 +00:00
|
|
|
#include "ui/gtk/main.h"
|
|
|
|
#include "ui/gtk/dlg_utils.h"
|
|
|
|
#include "ui/gtk/gui_utils.h"
|
|
|
|
#include "ui/gtk/tap_param_dlg.h"
|
|
|
|
#include "ui/gtk/service_response_time_table.h"
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
/* used to keep track of the statistics for an entire program interface */
|
|
|
|
struct camelsrt_t {
|
|
|
|
GtkWidget *win;
|
|
|
|
srt_stat_table camel_srt_table;
|
|
|
|
};
|
|
|
|
|
|
|
|
static void camelsrt_set_title(struct camelsrt_t * p_camelsrt);
|
|
|
|
static void camelsrt_reset(void *phs);
|
2010-08-30 16:10:01 +00:00
|
|
|
static int camelsrt_packet(void *phs,
|
2015-02-15 18:58:39 +00:00
|
|
|
packet_info *pinfo _U_,
|
|
|
|
epan_dissect_t *edt _U_,
|
|
|
|
const void *phi);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
static void camelsrt_draw(void *phs);
|
|
|
|
static void win_destroy_cb(GtkWindow *win _U_, gpointer data);
|
2012-12-05 15:56:36 +00:00
|
|
|
static void gtk_camelsrt_init(const char *opt_arg, void *userdata _U_);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
void register_tap_listener_gtk_camelsrt(void);
|
|
|
|
|
|
|
|
/*
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
static void camelsrt_set_title(struct camelsrt_t * p_camelsrt)
|
|
|
|
{
|
2012-06-03 22:03:05 +00:00
|
|
|
set_window_title(p_camelsrt->win, "CAMEL Service Response Time statistics");
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void camelsrt_reset(void *phs)
|
|
|
|
{
|
|
|
|
struct camelsrt_t *hs=(struct camelsrt_t *)phs;
|
|
|
|
reset_srt_table_data(&hs->camel_srt_table);
|
2010-08-30 16:10:01 +00:00
|
|
|
camelsrt_set_title(hs);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Count the delta time between Request and Response
|
|
|
|
* As we can make several measurement per message, we use a boolean array for the category
|
2010-08-30 16:10:01 +00:00
|
|
|
* Then, if the measurement is provided, check if it is valid, and update the table
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
*/
|
2010-08-30 16:10:01 +00:00
|
|
|
static int camelsrt_packet(void *phs,
|
2015-02-15 18:58:39 +00:00
|
|
|
packet_info *pinfo _U_,
|
|
|
|
epan_dissect_t *edt _U_,
|
|
|
|
const void *phi)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
|
|
|
struct camelsrt_t *hs=(struct camelsrt_t *)phs;
|
2014-01-15 08:38:14 +00:00
|
|
|
const struct camelsrt_info_t * pi=(const struct camelsrt_info_t *)phi;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i=1; i<NB_CAMELSRT_CATEGORY; i++) {
|
|
|
|
if ( pi->bool_msginfo[i] &&
|
2015-02-15 18:58:39 +00:00
|
|
|
pi->msginfo[i].is_delta_time
|
|
|
|
&& pi->msginfo[i].request_available
|
|
|
|
&& !pi->msginfo[i].is_duplicate ) {
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
add_srt_table_data(&hs->camel_srt_table, i, &pi->msginfo[i].req_time, pinfo);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
} /* category */
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void camelsrt_draw(void *phs)
|
|
|
|
{
|
|
|
|
struct camelsrt_t *hs=(struct camelsrt_t *)phs;
|
|
|
|
draw_srt_table_data(&hs->camel_srt_table);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Routine for Display
|
|
|
|
*/
|
|
|
|
static void win_destroy_cb(GtkWindow *win _U_, gpointer data)
|
|
|
|
{
|
|
|
|
struct camelsrt_t *hs=(struct camelsrt_t *)data;
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
remove_tap_listener(hs);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
free_srt_table_data(&hs->camel_srt_table);
|
|
|
|
g_free(hs);
|
|
|
|
}
|
|
|
|
|
2012-12-05 15:56:36 +00:00
|
|
|
static void gtk_camelsrt_init(const char *opt_arg, void *userdata _U_)
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
{
|
|
|
|
struct camelsrt_t * p_camelsrt;
|
2010-08-30 16:10:01 +00:00
|
|
|
const char *filter=NULL;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
GtkWidget *cmd_label;
|
|
|
|
GtkWidget *main_label;
|
|
|
|
GtkWidget *filter_label;
|
2007-11-28 03:04:09 +00:00
|
|
|
char *filter_string;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
GString *error_string;
|
|
|
|
GtkWidget *vbox;
|
|
|
|
GtkWidget *bbox;
|
|
|
|
GtkWidget *close_bt;
|
2015-02-04 04:27:01 +00:00
|
|
|
gchar* tmp_str;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
int i;
|
|
|
|
|
2012-12-05 15:56:36 +00:00
|
|
|
if(strncmp(opt_arg,"camel,srt,",10) == 0){
|
|
|
|
filter=opt_arg+10;
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
} else {
|
|
|
|
filter=NULL;
|
|
|
|
}
|
2010-08-30 16:10:01 +00:00
|
|
|
|
2013-03-21 02:58:59 +00:00
|
|
|
p_camelsrt=(struct camelsrt_t *)g_malloc(sizeof(struct camelsrt_t));
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
2009-06-21 20:42:07 +00:00
|
|
|
p_camelsrt->win= dlg_window_new("camel-srt"); /* transient_for top_level */
|
|
|
|
gtk_window_set_destroy_with_parent (GTK_WINDOW(p_camelsrt->win), TRUE);
|
|
|
|
|
Add a "Sum" column to the Service Response Time (SRT) window.
The Service Response Time (SRT) window currently provides the
columns: Index, Procedure, Calls, Min SRT, Max SRT, and Avg SRT.
A Sum column has been found useful in some customer situations
to understand the total time spent doing a set of procedures.
For example, in one case we were trying to isolate whether most
time was being spent on a client thread or in the act of making
outbound calls. We knew the start and end time of the client call,
so with the "Sum" of time spent in that period, we could isolate
a particular set of procedures driving the slow down.
Additional changes made in this patch:
* Add " (s)" to Min, Max, Avg, and Sum columns to make it clear
that times are in seconds.
* Refactor out width and height constants used in calls to
gtk_window_set_default_size in most of the SRT users into
#define SRT_PREFERRED_WIDTH and SRT_PREFERRED_HEIGHT. Also
increase the common width of 550 to 650 to account for the
additional column.
Change-Id: I20f152eecbcd0bbf69f71c6c6b9f9463e8867e23
Reviewed-on: https://code.wireshark.org/review/7047
Petri-Dish: Anders Broman <a.broman58@gmail.com>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Anders Broman <a.broman58@gmail.com>
2015-02-10 01:20:38 +00:00
|
|
|
gtk_window_set_default_size(GTK_WINDOW(p_camelsrt->win), SRT_PREFERRED_WIDTH, SRT_PREFERRED_HEIGHT);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
camelsrt_set_title(p_camelsrt);
|
|
|
|
|
2012-04-21 16:40:14 +00:00
|
|
|
vbox=ws_gtk_box_new(GTK_ORIENTATION_VERTICAL, 3, FALSE);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
gtk_container_add(GTK_CONTAINER(p_camelsrt->win), vbox);
|
|
|
|
gtk_container_set_border_width(GTK_CONTAINER(vbox), 12);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
main_label=gtk_label_new("CAMEL Service Response Time statistics");
|
|
|
|
gtk_box_pack_start(GTK_BOX(vbox), main_label, FALSE, FALSE, 0);
|
|
|
|
gtk_widget_show(main_label);
|
|
|
|
|
2007-11-28 03:04:09 +00:00
|
|
|
filter_string = g_strdup_printf("Filter: %s",filter ? filter : "");
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
filter_label=gtk_label_new(filter_string);
|
2007-11-28 03:04:09 +00:00
|
|
|
g_free(filter_string);
|
|
|
|
gtk_label_set_line_wrap(GTK_LABEL(filter_label), TRUE);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
gtk_box_pack_start(GTK_BOX(vbox), filter_label, FALSE, FALSE, 0);
|
|
|
|
gtk_widget_show(filter_label);
|
|
|
|
|
|
|
|
cmd_label=gtk_label_new("CAMEL Commands");
|
|
|
|
gtk_box_pack_start(GTK_BOX(vbox), cmd_label, FALSE, FALSE, 0);
|
|
|
|
gtk_widget_show(cmd_label);
|
|
|
|
|
|
|
|
/* We must display TOP LEVEL Widget before calling init_srt_table() */
|
|
|
|
gtk_widget_show_all(p_camelsrt->win);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
|
|
|
init_srt_table(&p_camelsrt->camel_srt_table, NB_CAMELSRT_CATEGORY, vbox, NULL);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
for(i=0 ;i<NB_CAMELSRT_CATEGORY; i++) {
|
2015-02-04 04:27:01 +00:00
|
|
|
tmp_str = val_to_str_wmem(NULL,i,camelSRTtype_naming,"Unknown (%d)");
|
|
|
|
init_srt_table_row(&p_camelsrt->camel_srt_table, i, tmp_str);
|
|
|
|
wmem_free(NULL, tmp_str);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
|
|
|
|
2010-08-30 16:10:01 +00:00
|
|
|
error_string=register_tap_listener("CAMEL",
|
2015-02-15 18:58:39 +00:00
|
|
|
p_camelsrt,
|
|
|
|
filter,
|
|
|
|
0,
|
|
|
|
camelsrt_reset,
|
|
|
|
camelsrt_packet,
|
|
|
|
camelsrt_draw);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
2009-06-05 22:42:47 +00:00
|
|
|
if(error_string){
|
|
|
|
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, "%s", error_string->str);
|
|
|
|
g_string_free(error_string, TRUE);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
g_free(p_camelsrt);
|
|
|
|
return;
|
|
|
|
}
|
2010-08-30 16:10:01 +00:00
|
|
|
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
/* Button row. */
|
|
|
|
bbox = dlg_button_row_new(GTK_STOCK_CLOSE, NULL);
|
|
|
|
gtk_box_pack_end(GTK_BOX(vbox), bbox, FALSE, FALSE, 0);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
2013-03-21 02:58:59 +00:00
|
|
|
close_bt = (GtkWidget *)g_object_get_data(G_OBJECT(bbox), GTK_STOCK_CLOSE);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
window_set_cancel_button(p_camelsrt->win, close_bt, window_cancel_button_cb);
|
2010-08-30 16:10:01 +00:00
|
|
|
|
2008-04-09 05:37:53 +00:00
|
|
|
g_signal_connect(p_camelsrt->win, "delete_event", G_CALLBACK(window_delete_event_cb), NULL);
|
|
|
|
g_signal_connect(p_camelsrt->win, "destroy", G_CALLBACK(win_destroy_cb), p_camelsrt);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
gtk_widget_show_all(p_camelsrt->win);
|
|
|
|
window_present(p_camelsrt->win);
|
2009-06-05 22:42:47 +00:00
|
|
|
cf_retap_packets(&cfile);
|
2011-07-21 20:12:08 +00:00
|
|
|
gdk_window_raise(gtk_widget_get_window(p_camelsrt->win));
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
|
|
|
|
}
|
|
|
|
|
2011-06-05 22:39:23 +00:00
|
|
|
static tap_param camel_srt_params[] = {
|
2014-11-14 20:21:12 +00:00
|
|
|
{ PARAM_FILTER, "filter", "Filter", NULL, TRUE }
|
2011-06-05 22:39:23 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
static tap_param_dlg camel_srt_dlg = {
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
"CAMEL Service Response Time",
|
|
|
|
"camel,srt",
|
|
|
|
gtk_camelsrt_init,
|
2011-06-05 22:39:23 +00:00
|
|
|
-1,
|
|
|
|
G_N_ELEMENTS(camel_srt_params),
|
|
|
|
camel_srt_params
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
void /* Next line mandatory */
|
|
|
|
register_tap_listener_gtk_camelsrt(void)
|
|
|
|
{
|
2013-05-24 01:10:16 +00:00
|
|
|
register_param_stat(&camel_srt_dlg, "CAMEL",
|
2015-02-15 18:58:39 +00:00
|
|
|
REGISTER_STAT_GROUP_RESPONSE_TIME);
|
From Florent.Drouin@alcatel.fr:
Please find two new TAP for Camel Statistics.
The first one updates counters related to camel operations. It is located in the GSM submenu. The second one , named Camel Service Response Time, gives the time ellapsed between a couple of camel specifics operations. (For example InitialDP/Continue or InitialDP GPRS/Continue GPRS). With Wireshark, you can have the Min/Max/Mean delay time for your traces files, and with Tshark, you have the additional information for percentile (1%,95% 99% etc )
To enable the use of the Camel statistics, you have 2 new parameters in the preferences,
- SRT, enable the service Response Time calculation.
- persistentSRT, keep the data in a context, even after the camel session has been closed. This is mandatory with Wireshark, to have a clean display of the stats.
Only the new files checked in for now because of include problems.
svn path=/trunk/; revision=19420
2006-10-03 22:12:47 +00:00
|
|
|
}
|
2015-02-15 18:58:39 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Editor modelines - http://www.wireshark.org/tools/modelines.html
|
|
|
|
*
|
|
|
|
* Local Variables:
|
|
|
|
* c-basic-offset: 2
|
|
|
|
* tab-width: 8
|
|
|
|
* indent-tabs-mode: nil
|
|
|
|
* End:
|
|
|
|
*
|
|
|
|
* vi: set shiftwidth=2 tabstop=8 expandtab:
|
|
|
|
* :indentSize=2:tabSize=8:noTabs=true:
|
|
|
|
*/
|