Hello,
I have started using observium and liked it a lot.
In syslog, I would propose a new option of searching for traps with a option to add a NOT, expecially in the priorities search.
Example:
All traps NOT informational.
Hi All
I have a few OSX servers and their OS is not detected. I looked in the distro script and see that it does not try to detect OSX. I did see an apple.png file in the images/os directory, so this make me wonder if anyone else has had success in OSX detection?
Thanks
Todd
Hi Paul,
That’s excellent thanks! I've just extended that array to include all our (already labelled, thankfully) ports for various service types and it's worked brilliantly.
One question, I don't suppose there is an 'easy' way to add a category which is made of up two other port types? Like with the default "Peering & Transit" group?
Cheers :)
Robert Williams
Custodian Data Centre
Email: Robert(a)CustodianDC.com
http://www.CustodianDC.com
-----Original Message-----
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Paul Orrock
Sent: 15 May 2013 06:00
To: Observium Network Observation System
Subject: Re: [Observium] Custom port service type?
Hi,
I've just supplied a patch to the nav bar (commit 4004) that will pick up anything you put followed by a colon and display it as a group under the ports menu. So I have a bunch of ports which have descriptions which start
ESXData:
Inter:
Mgmt:
etc and now those headings appear as groups under the port menu automatically when you add them to the config file with
$config['int_groups'] = array("EsxData","EsxMgmt","Inter");
If your existing ports don't start with something like that then you'll need to create a custom port description parser which will pull out the type from however you have it laid out in your port descriptions.
I took the opportunity to re-label all my 330 ports into a better structure and just use the standard parser but the custom parser is easy enough if you can write regular expressions.
regards,
Paul
On 15/05/2013 02:08, Jason Lixfeld wrote:
>
> On 2013-05-14, at 5:59 PM, Tom Laermans <tom.laermans(a)powersource.cx> wrote:
>
>> On 14/05/2013 23:45, Jason Lixfeld wrote:
>>> My port naming convention for core ports doesn't follow the "Core:" spec required by Observium. Is it possible to specify a custom type, or perhaps change the default? I'd love to see my core ports with a click of the Ports drop-down hopefully by avoiding having to reconfigure over 400 port descriptions. I can't see anything in defaults.inc.php and I'm not well enough versed in php to really know how to go about looking through the php code to try and find the answer. My google-fu is failing me too, so any pointers would be greatly appreciated.
>>>
>>
>> You can write a custom parser and set it in the config:
>>
>> $config['port_descr_parser'] = "includes/port-descr-parser.inc.php"; # Parse port descriptions into fields
>>
>> Take a look at that file, make a copy of it, and edit to your needs. It's not the prettiest code, heh - just opened it for the first time.
>>
>> Basically, the variables used there are the ones you can fill, particularly $type should be filled. $this_port['ifAlias'] is your interface description which you can parse in any way you like.
>
> I don't get it :( Observium shows core ports in the Ports > Core if the interface description starts with "Core:". I don't see any reference to Core: in that file to change it to reflect what my core facing interface descriptions say.
> _______________________________________________
> observium mailing list
> observium(a)observium.org
> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
>
_______________________________________________
observium mailing list
observium(a)observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
My port naming convention for core ports doesn't follow the "Core:" spec required by Observium. Is it possible to specify a custom type, or perhaps change the default? I'd love to see my core ports with a click of the Ports drop-down hopefully by avoiding having to reconfigure over 400 port descriptions. I can't see anything in defaults.inc.php and I'm not well enough versed in php to really know how to go about looking through the php code to try and find the answer. My google-fu is failing me too, so any pointers would be greatly appreciated.
Thanks in advance.
Getting the files in the right place is left as an exercise for the user.
:)
Rachid Zarouali <rzarouali(a)gmail.com> wrote:
>_______________________________________________
>observium mailing list
>observium(a)observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Smokeping isn't always 20 pings?
Well I never!
:)
Adam.
Robert Williams <Robert(a)CustodianDC.com> wrote:
>_______________________________________________
>observium mailing list
>observium(a)observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
Just setup Smokeping integration (and generated targets using Michiel’s groovy script – thanks!). Anyway, it’s all working fine for all the hosts but I’m not sure what the 3rd graph on the Ping tab is meant to show, called localhost. It appears on every single host’s “Ping” tab.
Have I just failed to configured a hostname *somewhere* or is this graph meant to display something else? When you click on it you just get an “Insufficient Permissions” message, image attached for reference.
Any input or pointers as to what I’ve done wrong are welcome – cheers :)
[cid:image001.png@01CE4E68.90BE29B0]
Robert Williams
Custodian Data Centre
Email: Robert(a)CustodianDC.com
http://www.CustodianDC.com
Hi,
Can any of the devs explain why Observium phones home (to
update.observium.org) when it runs discover.php? What data is being sent
and why isn't this behaviour explicitly mentioned anywhere in the docs or
on observium.org?
Thanks,
Dermot
User editing was turned off a year or two ago because of spam.
Running the script on every rrd is not advised. Only run it on things with spikes!
I'll have a look at the page.
Adam.
List User <list(a)redspeedservers.com> wrote:
>I didn't see how I can edit it so:
>http://www.observium.org/wiki/Removing_RRDTool_Spikes
>
>for i in rrds/*/*.rrd; do scripts/removespikes.pl $i; done;
>should be
>for i in rrd/*/*.rrd; do scripts/removespikes.pl $i; done;
>
>Changes: rrds -> rrd
>_______________________________________________
>observium mailing list
>observium(a)observium.org
>http://postman.memetic.org/cgi-bin/mailman/listinfo/observium