Mailing List Archive

Searching for ip-numbers in RT
Hi,


I have some trouble to get the free text (content I believe) search for
IP-numbers in RT correct. I/we have got about 24k tickets in our system.
When I search for a number it seems to be truncated in some way. Unclear
how.

Ex. (Edit Query mode)

( Content LIKE '127.0.0.2' )
Found 311 tickets

( Content LIKE '127.' )
Found 311 tickets

( Content LIKE '194.22.77.33' )
Found 2,944 tickets

( Content LIKE '194.' )
Found 2,944 tickets


I'm quite certain we have got a lot of tickets that has "127" in them.
We've probably no one with "194.22.77.33".
I've tried a number of ways to escape the characters but no luck. Double
quotes turn into single quotes so normal distinction between them is
off. Equal sign or LIKE is the same here. How do I construct a search
for IP-numbers in RT to get tickets with one explicit IP number?

PS. Search in Subject works as expected. DS

regards,


--

Bengt Gördén
Resilans AB


---------
RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training
* Los Angeles - January 9-11 2017
Re: Searching for ip-numbers in RT [ In reply to ]
Quoting Bengt Gördén <bengan@resilans.se>:

> Hi,
>
>
> I have some trouble to get the free text (content I believe) search for
> IP-numbers in RT correct. I/we have got about 24k tickets in our system.
> When I search for a number it seems to be truncated in some way. Unclear
> how.
>
> Ex. (Edit Query mode)
>
> ( Content LIKE '127.0.0.2' )
> Found 311 tickets
>
> ( Content LIKE '127.' )
> Found 311 tickets
>
> ( Content LIKE '194.22.77.33' )
> Found 2,944 tickets
>
> ( Content LIKE '194.' )
> Found 2,944 tickets
>
>
> I'm quite certain we have got a lot of tickets that has "127" in them.
> We've probably no one with "194.22.77.33".
> I've tried a number of ways to escape the characters but no luck. Double
> quotes turn into single quotes so normal distinction between them is
> off. Equal sign or LIKE is the same here. How do I construct a search
> for IP-numbers in RT to get tickets with one explicit IP number?
>
> PS. Search in Subject works as expected. DS
>
> regards,
>
>
> --
>
> Bengt Gördén

Hi,
What db and text search are you using? Postgresql definitely works for
this. Maybe there are some adjustments that you need to make.

Regards,
Ken


---------
RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training
* Los Angeles - January 9-11 2017
Re: Searching for ip-numbers in RT [ In reply to ]
Den 2016-11-19 kl. 20:28, skrev ktm@rice.edu:
> Quoting Bengt Gördén <bengan@resilans.se>:
>
>> Hi,
>>
>>
>> I have some trouble to get the free text (content I believe) search for
>> IP-numbers in RT correct. I/we have got about 24k tickets in our system.
>> When I search for a number it seems to be truncated in some way. Unclear
>> how.
>>
>> Ex. (Edit Query mode)
>>
>> ( Content LIKE '127.0.0.2' )
>> Found 311 tickets
>>
>> ( Content LIKE '127.' )
>> Found 311 tickets
>>
>> ( Content LIKE '194.22.77.33' )
>> Found 2,944 tickets
>>
>> ( Content LIKE '194.' )
>> Found 2,944 tickets
>>
>>
>> I'm quite certain we have got a lot of tickets that has "127" in them.
>> We've probably no one with "194.22.77.33".
>> I've tried a number of ways to escape the characters but no luck. Double
>> quotes turn into single quotes so normal distinction between them is
>> off. Equal sign or LIKE is the same here. How do I construct a search
>> for IP-numbers in RT to get tickets with one explicit IP number?
>>
>> PS. Search in Subject works as expected. DS
>>
>> regards,
>>
>>
>> --
>>
>> Bengt Gördén
>
> Hi,

Hi,

Sorry for the late reply.

> What db and text search are you using? Postgresql definitely works for
> this. Maybe there are some adjustments that you need to make.
>

mysql and sphinx. It might be some adjustments for sphinx that we
haven't figured out yet. Normal search seems to be no problem.


regards,


--

Bengt Gördén
Resilans AB


---------
RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/training
* Los Angeles - January 9-11 2017