ailto:[EMAIL PROTECTED] On Behalf Of Wes Nichols
> Sent: Tuesday, April 01, 2008 2:33 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Mysterious gap in log files.
>
>
> **
> I would add in SQL logging. I bet there is some DB activity that makes
> up for this gap.
>
> __
-
> *From:* Action Request System discussion list(ARSList) [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Wes Nichols
> *Sent:* Tuesday, April 01, 2008 2:33 PM
>
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: Mysterious gap in log files.
>
> ** I would add in SQL l
es Nichols
Sent: Tuesday, April 01, 2008 2:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mysterious gap in log files.
**
I would add in SQL logging. I bet there is some DB activity that makes
up for this gap.
From: Action Request System discussion list(ARSList)
[mai
. There's zero activity.
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Wes Nichols
Sent: Tuesday, April 01, 2008 2:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mysterious gap in log files.
**
I would add in SQL
is gap.
>
>
>
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow
> Sent: Tuesday, April 01, 2008 2:12 PM
> To: arslist@ARSLIST.ORG
> Subject: Re: Mysterious gap in log files.
>
>
> **
> Un
Subject: Re: Mysterious gap in log files.
**
Unfortunately there's nothing in the API log to show - it calls +CE on
HPD:Help Desk to create the entry - the next item in the API log is
after the entry is created. That's a 39 second stretch during which the
filter items I mentioned are
Axton
Sent: Tuesday, April 01, 2008 1:07 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mysterious gap in log files.
** Post the filter/api log snippets that show the gap with the TID and
RPC ID included.
Axton
On Tue, Apr 1, 2008 at 12:32 PM, William Rentfrow
<[EMAIL PROTECTED]> wrote:
Post the filter/api log snippets that show the gap with the TID and RPC ID
included.
Axton
On Tue, Apr 1, 2008 at 12:32 PM, William Rentfrow <
[EMAIL PROTECTED]> wrote:
> ** I am trying to tighten up the time it takes to create a new Incident in
> IM 7.03 (ARS 7.01, Solaris, remote oracle DB).
>
I am trying to tighten up the time it takes to create a new Incident in
IM 7.03 (ARS 7.01, Solaris, remote oracle DB).
I've checked the threads/queues quite thoroughly and they appears to be
fine - there's plenty of available time queue time. However, in the
filter log there are multiple places
9 matches
Mail list logo
