[rt-users] profiling/monitoring on requesttracker
Hi All, I want to monitor the performance of my requesttracker and I wanted to ask the folks here if there exists any tool which can help in profiling/monitoring the performance of requesttracker. It would be very help if someone could provide recommended tune-ups for improving the performance. Thanks and Regards Srinath Kotu
Re: [rt-users] profiling/monitoring on requesttracker
On Wed, Apr 15, 2015 at 12:42:38PM +, Kotu, Srinath wrote: > Hi All, > > I want to monitor the performance of my requesttracker and I wanted to ask > the folks here if there exists any tool which can help in > profiling/monitoring the performance of requesttracker. It would be very help > if someone could provide recommended tune-ups for improving the performance. > > Thanks and Regards > Srinath Kotu Hi, Probably the most important thing to monitor in RT is the performance of the database queries, since the performance of the user interface directly reflects that. Based on your choice of backend, take advantage of its "slow query logging" to analyze it performance. For PostgreSQL, pgbadger is useful for drilling down and identifying performance issues. Regards, Ken
[rt-users] Set default queue for Quick ticket creation?
We currently have RT 4.2.10 up and running, and have the Quick ticket creation widget on our users home screens. Is there a way to change the default queue in the dropdown for QuickCreate? Users are not being mindful to switch queues before submitting, and I really don't want to rename all my queues to impose a sort order. Thanks!
[rt-users] custom template help
Hi, Rt 4.2.10 We have a number of automated processes that generate emails into our helpdesk. The "From" of these messages is the process user and not a live requestor. For example, we have a process that finds all the customers who's accounts have been deactivated since the last time the report was run. For each deactivated account found an email message is sent to the helpdesk queue responsible for dealing with these things. The emails are each plain text. The body of each message contains the customer's Full_Name, Email_Address, Account_End_Date. Something like: Account deactivation notice for customer Alice Aubrey (aaub...@mycompany.com). Account deactivated on 2015-02-20 13:00:00 This can be reformatted easily so I am not concerned about that. I would like a template that can be associated with the "On Resolve" action that will harvest the Full_Name, Email_Address, Account_End_Date fields above and then create an outbound message to the customer that says something like: Subject: Account deactivation for Alice Aubrey CC: aaub...@mycompany.com Content-Type: text/html Dean Alice Aubrey, This is to notify you that your account with us was deactivated on 2015-02-20 13:00:00 I have tried creating a template that tries to parse the $Ticket->_RecordNote field but I'm not sure that is the way to go... because it didn't work :) 1) What is the best way to harvest data from the initial ticket body for use in an outbound template 2) Is it OK to CC in the template as I suggested above?
Re: [rt-users] Improper display of ticket transaction's HTML
An update, below, on this issue in case anyone comes across it. Seems
like a bug to me.
On 3/19/2015 9:16 AM, Jeff Blaine wrote:
> On 3/11/2015 3:56 AM, Christian Loos wrote:
>> Hi,
>>
>> upgrading to a more recent version of RT and installing HTML::Gumbo
>> gives you tables in transactions (RT supports this since 4.2.6) [1].
>>
>> If you can't upgrade, you can use RT::Extension::PermissiveHTMLMail [2].
>>
>> Chris
>>
>> [1] https://www.bestpractical.com/docs/rt/4.2/RT_Config.html#PreferRichText
>> [2] https://github.com/bestpractical/rt-extension-permissivehtmlmail
>
> GOOD:
>
> We've updated our test server to RT 4.2.10 and installed HTML::Gumbo per
> the notes in the documentation for $PreferRichText. When
> local/lib/RT/Interface/Web_Local.pm is configured to allow various table
> attributes, including 'style', the transaction HTML now displays as a
> table properly!
>
> BAD:
>
> But now there are various html, head, body tags on what seems to be only
> search result blocks.
>
> IIRC, image attachments are not allowed to the list. Here are 2
> screenshots showing what I am talking about in case anyone wants to see:
>
> https://www.dropbox.com/s/euca82h6qfagki1/rt-4210-broken.jpg?dl=0
>
> https://www.dropbox.com/s/ym2ctowlo8qhmnf/rt-4210-broken2.jpg?dl=0
This problem goes away if I uninstall HTML::Gumbo
>> Am 10.03.2015 um 20:35 schrieb Jeff Blaine:
>>> Hi,
>>>
>>> We're using RT 4.2.5 (for now).
>>>
>>> $PreferRichText is turned on.
>>>
>>> We've put in place a Web_Local.pm that is allowing all tags via:
>>>
>>> push @SCRUBBER_ALLOWED_TAGS, qw('*');
>>>
>>> Something is still mucking with our HTML though, specifically (that
>>> we've found so far) various table tags' attributes like borders and
>>> padding seem to not be rendered properly. The table borders don't render
>>> at all.
>>>
>>> Any ideas?
>>>
>>> It is a little unclear to me exactly how to use
>>> %SCRUBBER_ALLOWED_ATTRIBS ... setting it to {'*', 1} caused various
>>> links in the web UI to not work anymore.
>>>
>>
>
--
Jeff Blaine
kickflop.net
PGP/GnuPG Key ID: 0x0C8EDD02
