iTop has a “native” integration to Nagios thru a plugin to create tickets automatically, does anyone know if there is a way to integrate it with observium?
Thanks!
This email is confidential and / or may contain inside information. If you are not the addressee or authorized to receive your emails, you must NOT use, copy, disclose or take any action based on this email or any other information herein, please notify the sender immediately by reply this email and delete this email and its attachments.Privacy note a: www.wynnmex.com Este correo electrónico es confidencial y/o puede contener información privilegiada. Si usted no es su destinatario o no es alguna persona autorizada por éste para recibir sus correos electrónicos, NO deberá utilizar, copiar, relevelar o tomar ninguna acción basada en este correo o cualquier otra información incluida en el, favor de notificar al remitente de inmediato mediante el envío de este correo y borrar a continuación totalmente este correo y sus anexos. Consulta nuestro aviso de privacidad en:www.wynnmex.com
This would require someone to write a notification transport to create tickets on itop.
Their API seems to be very... complex and overly generic. You seem to have to pass SQL statements to it to create tickets, which is something I've never seen before.
https://www.itophub.io/wiki/page?id=2_3_0:advancedtopics:create_ticket
If you're lucky Mike might be interested in adding support for this, but someone might need to provide him with an itop installation to test with.
Adam.
Luis Olavarrieta via observium wrote on 12/01/2023 18:36:
iTop has a “native” integration to Nagios thru a plugin to create tickets automatically, does anyone know if there is a way to integrate it with observium?
Thanks!
signature_2307061704 http://www.wynnmex.com/
This email is confidential and / or may contain inside information. If you are not the addressee or authorized to receive your emails, you must NOT use, copy, disclose or take any action based on this email or any other information herein, please notify the sender immediately by reply this email and delete this email and its attachments.Privacy note a: www.wynnmex.com
Este correo electrónico es confidencial y/o puede contener información privilegiada. Si usted no es su destinatario o no es alguna persona autorizada por éste para recibir sus correos electrónicos, NO deberá utilizar, copiar, relevelar o tomar ninguna acción basada en este correo o cualquier otra información incluida en el, favor de notificar al remitente de inmediato mediante el envío de este correo y borrar a continuación totalmente este correo y sus anexos. Consulta nuestro aviso de privacidad en:www.wynnmex.com
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Is it possible to take me out of this e-mail group?
-- Arlina Morina Informations Management und Einkauf DMT-Gesellschaft für Lehre und Bildung mbH Herner Straße 45 44787 Bochum +49 (234) 968 8284 Arlina.Morina@dmt-lb.demailto:Arlina.Morina@dmt-lb.de https://www.dmt-lb.de Sitz der Gesellschaft: Bochum Registergericht: Amtsgericht Bochum | Handelsregister: B 4052 Geschäftsführung: Prof. Susanne Lengyel (Vorsitzende), Prof. Dr. Sunhild Kleingärtner, Ulrich Wessel Vorsitzende des Beirates: Bärbel Bergerhoff-Wodopia Klicken Sie hierhttps://datenschutz.thga.de/extern für unsere Datenschutzhinweise. Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail drucken. Von: Adam Armstrong via observium observium@lists.observium.org Gesendet: Dienstag, 17. Januar 2023 07:38 An: Luis Olavarrieta via observium observium@lists.observium.org Cc: Adam Armstrong adama@observium.org Betreff: [Observium] Re: integration with iTop
This would require someone to write a notification transport to create tickets on itop.
Their API seems to be very... complex and overly generic. You seem to have to pass SQL statements to it to create tickets, which is something I've never seen before.
https://www.itophub.io/wiki/page?id=2_3_0:advancedtopics:create_ticket
If you're lucky Mike might be interested in adding support for this, but someone might need to provide him with an itop installation to test with.
Adam.
Luis Olavarrieta via observium wrote on 12/01/2023 18:36:
iTop has a “native” integration to Nagios thru a plugin to create tickets automatically, does anyone know if there is a way to integrate it with observium?
Thanks!
[signature_2307061704]http://www.wynnmex.com/
This email is confidential and / or may contain inside information. If you are not the addressee or authorized to receive your emails, you must NOT use, copy, disclose or take any action based on this email or any other information herein, please notify the sender immediately by reply this email and delete this email and its attachments.Privacy note a: www.wynnmex.comhttp://www.wynnmex.com
Este correo electrónico es confidencial y/o puede contener información privilegiada. Si usted no es su destinatario o no es alguna persona autorizada por éste para recibir sus correos electrónicos, NO deberá utilizar, copiar, relevelar o tomar ninguna acción basada en este correo o cualquier otra información incluida en el, favor de notificar al remitente de inmediato mediante el envío de este correo y borrar a continuación totalmente este correo y sus anexos. Consulta nuestro aviso de privacidad en:www.wynnmex.com
_______________________________________________
observium mailing list -- observium@lists.observium.orgmailto:observium@lists.observium.org
To unsubscribe send an email to observium-leave@lists.observium.orgmailto:observium-leave@lists.observium.org
-- Sent from Postboxhttps://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
Hello! Subscriber here... One of our Observium instances has stopped alerting on the port down alert/checker. Specifically, it will still alert in ports we had configured already when this instance of Observium was installed, but it will not alert on any new ports we configure/add to the infrastructure. I.e. switch1 port1 was set up right after install, tested, good, and still alerts if it goes down. switch1 port2 was added to observium at a later date due to a new server install, and if it goes down it will not alert. We had 8 switches at the time, and this behavior seems to be equal across all 8 (not had time for thorough testing, which I would normally do except for the discovery of the below error).
It has been going on for a few months that we know of, but this has not yet bubbled to the top of our list of things to tackle. But we are now adding new infrastructure to that particular datacenter, and while I am mucking about there I thought I would take a look.
I found the observium and housekeeping logs seemingly normal, but the db log is full of the below error (and nothing else):
[2023/01/17 22:53:56 +0000] index.php(40131): Failed dbQuery (#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND 0 GROUP BY `group_id`' at line 1), Query: SELECT COUNT(*) AS `count`, `group_id` FROM `group_table` WHERE AND 0 GROUP BY `group_id`
I thought this may have started when I did an update several months ago, but it is possible it has been doing this since inception. I did do an update today, thinking perhaps I missed running discovery.php -u when I did that update, but alas that did not help.
Help please. 😀
Helmut Fritz Director, Programs Cirrascale Cloud Services
actually, after digging into my history i may have found the cause: our hard drive filled up (seemingly database logs) and jammed up the database. i have set them to be circular (I believe, will follow up on that) but that is likely the timing of the start of those messages. is there a method to check the health of the database?
is there a method to reinstall and save the setup that is currently there? that might just be faster/easier than anything else!
thx!
Helmut
------ Original Message ------ From "Helmut Fritz" <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Date 1/17/2023 5:02:18 PM Subject dbquery failure
Hello! Subscriber here... One of our Observium instances has stopped alerting on the port down alert/checker. Specifically, it will still alert in ports we had configured already when this instance of Observium was installed, but it will not alert on any new ports we configure/add to the infrastructure. I.e. switch1 port1 was set up right after install, tested, good, and still alerts if it goes down. switch1 port2 was added to observium at a later date due to a new server install, and if it goes down it will not alert. We had 8 switches at the time, and this behavior seems to be equal across all 8 (not had time for thorough testing, which I would normally do except for the discovery of the below error).
It has been going on for a few months that we know of, but this has not yet bubbled to the top of our list of things to tackle. But we are now adding new infrastructure to that particular datacenter, and while I am mucking about there I thought I would take a look.
I found the observium and housekeeping logs seemingly normal, but the db log is full of the below error (and nothing else):
[2023/01/17 22:53:56 +0000] index.php(40131): Failed dbQuery (#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND 0 GROUP BY `group_id`' at line 1), Query: SELECT COUNT(*) AS `count`, `group_id` FROM `group_table` WHERE AND 0 GROUP BY `group_id`
I thought this may have started when I did an update several months ago, but it is possible it has been doing this since inception. I did do an update today, thinking perhaps I missed running discovery.php -u when I did that update, but alas that did not help.
Help please. 😀
Helmut Fritz Director, Programs Cirrascale Cloud Services
If you don’t care about historical data, config.php is really all that matters, you could blow it away and re-add all the devices and start fresh in an hour or so.
________________________________ Spencer J. Ryan| Manager, Technology and Infrastructure Miller Canfield T +1.313.496.7979 | F +1.313.496.7500 ________________________________
From: Helmut Fritz via observium observium@lists.observium.org Sent: Tuesday, January 17, 2023 8:21 PM To: Observium observium@lists.observium.org Cc: Helmut Fritz helmut.fritz@cirrascale.com Subject: [Observium] Re: dbquery failure
Caution: This is an external email. Do not open attachments or click links from unknown or unexpected emails.
actually, after digging into my history i may have found the cause: our hard drive filled up (seemingly database logs) and jammed up the database. i have set them to be circular (I believe, will follow up on that) but that is likely the timing of the start of those messages. is there a method to check the health of the database?
is there a method to reinstall and save the setup that is currently there? that might just be faster/easier than anything else!
thx!
Helmut
------ Original Message ------ From "Helmut Fritz" <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Date 1/17/2023 5:02:18 PM Subject dbquery failure
Hello! Subscriber here... One of our Observium instances has stopped alerting on the port down alert/checker. Specifically, it will still alert in ports we had configured already when this instance of Observium was installed, but it will not alert on any new ports we configure/add to the infrastructure. I.e. switch1 port1 was set up right after install, tested, good, and still alerts if it goes down. switch1 port2 was added to observium at a later date due to a new server install, and if it goes down it will not alert. We had 8 switches at the time, and this behavior seems to be equal across all 8 (not had time for thorough testing, which I would normally do except for the discovery of the below error).
It has been going on for a few months that we know of, but this has not yet bubbled to the top of our list of things to tackle. But we are now adding new infrastructure to that particular datacenter, and while I am mucking about there I thought I would take a look.
I found the observium and housekeeping logs seemingly normal, but the db log is full of the below error (and nothing else):
[2023/01/17 22:53:56 +0000] index.php(40131): Failed dbQuery (#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND 0 GROUP BY `group_id`' at line 1), Query: SELECT COUNT(*) AS `count`, `group_id` FROM `group_table` WHERE AND 0 GROUP BY `group_id`
I thought this may have started when I did an update several months ago, but it is possible it has been doing this since inception. I did do an update today, thinking perhaps I missed running discovery.php -u when I did that update, but alas that did not help.
Help please. 😀
Helmut Fritz Director, Programs Cirrascale Cloud Services
You have received a message from the law firm Miller Canfield. The information contained in or attached to this electronic mail may be privileged and/or confidential. If you received this transmission and are not the intended recipient, you should not read this message and are hereby notified that any dissemination, distribution or copying of this communication and/or its attachments is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and delete or destroy the original and any copies, electronic, paper or otherwise, that you may have of this communication and any attachments.
Ryan, Thank you. No way to save the device and alert setup?
Helmut
------ Original Message ------ From "Ryan, Spencer J. via observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Cc "Ryan, Spencer J." <Ryan@millercanfield.commailto:Ryan@millercanfield.com> Date 1/17/2023 5:39:50 PM Subject [EXTERNAL] [Observium] Re: dbquery failure
If you don’t care about historical data, config.php is really all that matters, you could blow it away and re-add all the devices and start fresh in an hour or so.
________________________________ Spencer J. Ryan| Manager, Technology and Infrastructure Miller Canfield T +1.313.496.7979 | F +1.313.496.7500 ________________________________
From: Helmut Fritz via observium <observium@lists.observium.orgmailto:observium@lists.observium.org> Sent: Tuesday, January 17, 2023 8:21 PM To: Observium <observium@lists.observium.orgmailto:observium@lists.observium.org> Cc: Helmut Fritz <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> Subject: [Observium] Re: dbquery failure
Caution: This is an external email. Do not open attachments or click links from unknown or unexpected emails.
actually, after digging into my history i may have found the cause: our hard drive filled up (seemingly database logs) and jammed up the database. i have set them to be circular (I believe, will follow up on that) but that is likely the timing of the start of those messages. is there a method to check the health of the database?
is there a method to reinstall and save the setup that is currently there? that might just be faster/easier than anything else!
thx!
Helmut
------ Original Message ------ From "Helmut Fritz" <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Date 1/17/2023 5:02:18 PM Subject dbquery failure
Hello! Subscriber here... One of our Observium instances has stopped alerting on the port down alert/checker. Specifically, it will still alert in ports we had configured already when this instance of Observium was installed, but it will not alert on any new ports we configure/add to the infrastructure. I.e. switch1 port1 was set up right after install, tested, good, and still alerts if it goes down. switch1 port2 was added to observium at a later date due to a new server install, and if it goes down it will not alert. We had 8 switches at the time, and this behavior seems to be equal across all 8 (not had time for thorough testing, which I would normally do except for the discovery of the below error).
It has been going on for a few months that we know of, but this has not yet bubbled to the top of our list of things to tackle. But we are now adding new infrastructure to that particular datacenter, and while I am mucking about there I thought I would take a look.
I found the observium and housekeeping logs seemingly normal, but the db log is full of the below error (and nothing else):
[2023/01/17 22:53:56 +0000] index.php(40131): Failed dbQuery (#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND 0 GROUP BY `group_id`' at line 1), Query: SELECT COUNT(*) AS `count`, `group_id` FROM `group_table` WHERE AND 0 GROUP BY `group_id`
I thought this may have started when I did an update several months ago, but it is possible it has been doing this since inception. I did do an update today, thinking perhaps I missed running discovery.php -u when I did that update, but alas that did not help.
Help please. 😀
Helmut Fritz Director, Programs Cirrascale Cloud Services
You have received a message from the law firm Miller Canfield. The information contained in or attached to this electronic mail may be privileged and/or confidential. If you received this transmission and are not the intended recipient, you should not read this message and are hereby notified that any dissemination, distribution or copying of this communication and/or its attachments is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and delete or destroy the original and any copies, electronic, paper or otherwise, that you may have of this communication and any attachments.
participants (5)
-
Adam Armstrong -
Helmut Fritz -
Luis Olavarrieta -
Morina, Arlina -
Ryan, Spencer J.