once you login, some data about what you do is temporarily stored until you
logout. the data is stored in the sessions table and you can see all active
sessions in admin interface, sessions module. if a user doesn't interact
with otrs for a configurable amount of time his session expires, all
sessi
On Sat, Sep 28, 2013 at 6:22 AM, Bogdan Iosif wrote:
> you need to monitor apache's access log or [temporarily] configure
> convenient timeouts for agent sessions and then monitor otrs db's sessions
> table. first choice is likely more suitable.
>
Thanks Bogdan for the quick reply. I am not sure
you need to monitor apache's access log or [temporarily] configure
convenient timeouts for agent sessions and then monitor otrs db's sessions
table. first choice is likely more suitable.
On Sep 28, 2013 3:46 AM, "Kaushal Shriyan" wrote:
>
>
>
> On Tue, Sep 24, 2013 at 8:59 PM, Kaushal Shriyan >
On Tue, Sep 24, 2013 at 8:59 PM, Kaushal Shriyan
wrote:
> Hi,
>
> Is there a way to check if otrs ticketing dashboard is being used by
> Agents at a specific moment of time period for example around 11:00 pm in
> the night?
>
> I am using select count(*) from ticket in mysql database to see for an
There are some packages that are not listed in the site, but is listed in the
ftp:
http://ftp.otrs.org/pub/otrs/packages/
There are a ChangeManagement 3.2.9 that use framework 3.2.
(Sorry for my poor English)
Atenciosamente: Robson Massaki Kobayashi
- Mensagem original -
Hi,
I have upgraded my installation from 3.1 to 3.2 and upgraded my ITSM
packages to via a remote repository.
I still have an error on : "ITSM 3.1.4 - Package not correctly deployed!
Please reinstall the package."
I have ITSMChangeManagement, Incident. all upgraded but I still have
a componen
Option 2 from my previous email *is* compatible with upgrades because it
requires implementation of an event module, which doesn't involve any
changes in files shipped with OTRS. You will need to perform these unwanted
changes only if you need to remove columns that don't support removal via
SysCon
Hi list,
I have a situation where I'd like to have the SystemMonitoring module handle
almost identical tickets in multiple queues.
With my current config, it doesn' work so well.
Here's what happens:
A host or service goes down somewhere, and our monitoring software sends two
(almost) identical
Op 27-9-2013 8:26, Claudio Kuenzler schreef:
Thanks a lot for all your input. I knew I'd get some advice here sooner
or later ;-).
If I find the time I'll look into adapting the code - problem will be
that it won't be compatible for future releases (will have to re-apply
the patch for every relea
