Hi Sivasamy, Tested extensively today, upto 25ms for a longer period without any problems. Thank you for a great and useful plugin.
Arie. Op woensdag 8 juli 2015 23:14:44 UTC+2 schreef Arie: > > Sivasamy, > > I'm testing with a 2sec interval, and let it run for the night. > > Thank you for working on it so fast. > > Arie. > > Op woensdag 8 juli 2015 16:58:29 UTC+2 schreef Sivasamy Kaliappan: >> >> Aire, >> >> I have fixed hang and too many threads issue. I have tested with 50 ms >> interval and a timeout of 20 seconds (higher timeout is due to some issue >> in the 3rdparty library) and it work fine. >> >> Get the latest jar >> <https://github.com/sivasamyk/graylog2-plugin-input-httpmonitor/raw/master/graylog2-plugin-input-httpmonitor-1.0.0.jar> >> >> and let me know your feedback. >> >> Thanks for your feedback. >> >> Regards, >> Siva. >> >> On Wednesday, July 8, 2015 at 5:27:45 PM UTC+5:30, Arie wrote: >>> >>> Sivasamy. >>> >>> Thank you for your reaction. >>> >>> another thing is that with the old and the newer version my Treads are >>> increasing and going sky hi. >>> Normally this is 700 - 1000, but i have numbers from 4000 upto 12360 >>> >>> hth,, >>> >>> Arie >>> >>> On Wednesday, July 8, 2015 at 8:33:24 AM UTC+2, Sivasamy Kaliappan wrote: >>>> >>>> Arie, >>>> >>>> The configuration page is in a different structure every time i select >>>> it. >>>> >>>> Siva>> I assume you are talking about the order of the fields listed in >>>> input configuration window. This is fixed as part of #1282 >>>> <https://github.com/Graylog2/graylog2-server/issues/1282> in >>>> graylog-server >>>> >>>> Graylog is heaving pain when i configure 20ms for example. Gives me >>>> this error >>>> >>>> Siva>> I agree 20 ms is too small an interval. I will check my local >>>> setup with this config. >>>> >>>> On Wednesday, July 8, 2015 at 1:27:53 AM UTC+5:30, Arie wrote: >>>>> >>>>> Hi Sivasamy, >>>>> >>>>> In testing it experience the following. The configuration page is in a >>>>> different structure >>>>> every time i select it. The items are not listed the same list each >>>>> time. Maybe due to the following: >>>>> >>>>> Graylog is heaving pain when i configure 20ms for example. Gives me >>>>> this error, >>>>> >>>>> "You are creating too many HashedWheelTimer instances. >>>>> HashedWheelTimer is a shared resource that must be reused across the >>>>> application, so that only a few instances are created." >>>>> >>>>> Looks like setting in milliseconds is to intensive for graylog it is >>>>> giving the " SharedResourceMisuseDetector" error, >>>>> and my memory is filled up like crazy. >>>>> >>>>> Setting the interval in seconds (even one second) is fine here. >>>>> >>>>> I don't see it as a replacement for the logs, but rather for >>>>> testing/monitoring (functionality) purposes. Thank you :-) >>>>> >>>>> hth,, >>>>> >>>>> Arie >>>>> >>>>> >>>>> Op dinsdag 7 juli 2015 09:29:01 UTC+2 schreef Sivasamy Kaliappan: >>>>>> >>>>>> Oops.. Here is the right link: >>>>>> https://github.com/sivasamyk/graylog2-plugin-input-httpmonitor >>>>>> >>>>>> On Tuesday, July 7, 2015 at 1:14:41 AM UTC+5:30, Arie wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> beware of the dot in the url :-) >>>>>>> >>>>>>> Op maandag 6 juli 2015 18:49:57 UTC+2 schreef Sivasamy Kaliappan: >>>>>>>> >>>>>>>> Hello All, >>>>>>>> >>>>>>>> I have developed a HTTP monitor plugin for graylog for monitoring >>>>>>>> HTTP URLs. >>>>>>>> Try the plugin and post your feedback here >>>>>>>> >>>>>>>> https://github.com/sivasamyk/graylog2-plugin-input-httpmonitor. >>>>>>>> >>>>>>>> If you find any issues or have new features, open a new github >>>>>>>> issue. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Siva. >>>>>>>> >>>>>>> -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
