Re: [SLUG] Job Management Apps
RT is capable of this with a little massaging: http://bestpractical.com/rt/ You can use custom fields, and due date and time worked etc. The due dates can be exported as ICS and imported into Google Calendar easily enough. My company provides commercial support for RT these days if you are interested. It does take some getting used to though - If you don't have the operational rigour to make it work, its a waste of time. Which is probably true for many systems. -- Regards, Dave Kempe - Original Message - > From: "Nigel Allen" > To: "Slug" > Sent: Wednesday, 9 May, 2012 4:06:50 PM > Subject: [SLUG] Job Management Apps > > > Hi All > > I've been looking for an application for a while that can be used for > a > handyman service - but a handyman service with a difference. > > Basically the handyman receives work orders from a Strata Management > or > Real Estate company to contact John Smith of so and such address and > telephone number to arrange for some repairs to be carried out. > > Bear in mind that there are usually multiple jobs being done > simultaneously. > > * First task is to contact the person in question and arrange an > appointment. This often takes several calls. > * Sometimes the repairs are specified in the work order but often > they > are not and a first appointment is usually necessary just to > establish the extent of the work. > * Sometimes there is a quotation required which goes back to the > managing company - other times it's just "do and charge". > * A second appointment is often necessary to perform the work > although > of the planet align the job may be done and completed during the > first appointment. > * Often the job involves time and materials, sometimes it's just > labour. > * Finally the job has to be invoiced back to the management > company. > Currently invoicing is done in MYOB and I'm happy to leave that > as > it is. > > Whatever we can come up with would ideally have an android client or > at > least sync with Google calendar for appointments and / or follow ups. > I > was looking at SugarCRM but I think that that is a little sledge > hammer > / nut for this. > > Any suggestions? Any Ideas? Any thought? > > TIA > > Nigel. > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open source log analyser tools (or: Alternatives to Splunk)
On 9 May 2012 19:23, Daniel Solsona wrote: > With logstash you have an agent in each server. There you can configure > inputs, filters and outputs. > > Inputs: file, syslog, etc > Filters: grep, regexp. Here you can do magic. > Outputs: file, elasticsearch, redis, amqp, etc (lots of possibilities) > > Check the docs to see if there is any filter/output that works for you. > > I reckon you can do what you need with logstash. But you can probably do > the same with some scripts. > We want a nice front end for helpdesk, plus we'd like to potentially roll it out to other aspects of the business. BI is something that would be a good value add to sell as well :) -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open source log analyser tools (or: Alternatives to Splunk)
With logstash you have an agent in each server. There you can configure inputs, filters and outputs. Inputs: file, syslog, etc Filters: grep, regexp. Here you can do magic. Outputs: file, elasticsearch, redis, amqp, etc (lots of possibilities) Check the docs to see if there is any filter/output that works for you. I reckon you can do what you need with logstash. But you can probably do the same with some scripts. On May 9, 2012 5:26 PM, "Mark Walkom" wrote: -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open source log analyser tools (or: Alternatives to Splunk)
On 9 May 2012 17:13, Daniel Solsona wrote: > Hi, > > It really depends on what are your needs. > We want to track a file as it hits our comms server (via FTP/HTTP), transfers to our app server, processes and is then generated out to the comms server and then picked up by the recipient. That will use the following logs; 1. FTP/HTTP daemon 2. FTP process 3. Application processing (x2, in then out) 1. Here we will probably have to link the in and out process using some database queries 4. FTP process 5. FTP/HTTP daemon It's convoluted, but our architecture restricts what we can do, and I don't know if we can make enough changes in the time I have to make it easier. I can probably create the parser I mentioned earlier. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open source log analyser tools (or: Alternatives to Splunk)
Hi, It really depends on what are your needs. I don't know much about the fancy things from splunk, but you can do some cool things with logstash. There is also a nice ui for logstash, kibana ( https://github.com/rashidkpc/Kibana) On 9 May 2012 17:04, Mark Walkom wrote: > We're looking at 2G a day, which is AUS$30K a year. And were on the S end > of SME so it's a hell of a lot. > > The only way we could cut this amount down would be is if we wrote a > customer parser that read the application logs that cut out all the > replicated crap (mostly environment variable stuff) and spat out the logs > to a separate dir for splunk to read. > But then we need to deal with extra storage requirements. > > Again, when you are a small operation with a small budget, money rules. > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Open source log analyser tools (or: Alternatives to Splunk)
We're looking at 2G a day, which is AUS$30K a year. And were on the S end of SME so it's a hell of a lot. The only way we could cut this amount down would be is if we wrote a customer parser that read the application logs that cut out all the replicated crap (mostly environment variable stuff) and spat out the logs to a separate dir for splunk to read. But then we need to deal with extra storage requirements. Again, when you are a small operation with a small budget, money rules. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
