What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" milton@valvesoftware.com To: "observium@observium.org" observium@observium.org Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
Here are some pointers:
- Device dropdown (instead of types perhaps?) - Matching group in alert checkers - Access granting for users complementing the device-based ones - Alerting address/contact per group - ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote:
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far! I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types. Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow. adam. ------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.com mailto:milton@valvesoftware.com> To: "observium@observium.org" <observium@observium.org mailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items - replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.orgmailto:adama@memetic.org>, Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?) - Matching group in alert checkers - Access granting for users complementing the device-based ones - Alerting address/contact per group - ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote: The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.commailto:milton@valvesoftware.com> To: "observium@observium.org"mailto:observium@observium.org <observium@observium.orgmailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation.
This was one of my ideas too. Using groups to replace device type.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 15:54:15 "Pedersen, Sean" spedersen@io.com wrote:
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items - replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.orgmailto:adama@memetic.org>, Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?)
- Matching group in alert checkers
- Access granting for users complementing the device-based ones
- Alerting address/contact per group
- ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote: The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.commailto:milton@valvesoftware.com> To: "observium@observium.org"mailto:observium@observium.org <observium@observium.orgmailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
observium mailing list observium@observium.orgmailto:observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Some examples:
- All devices of type X in the network
- All devices in room Y
- All devices of type X in datacentre Z.
- All devices in the first cabinet of each cabinet row in the network
- All ports used by customer XYZ
- All network items ordered in 2014
- You name it, it really depends on how good people are with setting up their conventions.
I can already do all of the above filtering, thanks to your groups system.
However, tell me if I'm wrong, the filters and the search function are not looking for vlan details.
Some networks have thousands of vlans and it might be handy to have a search/grouping for that too.
Cheers,
Marco
________________________________ From: observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org Sent: 12 November 2014 23:23 To: Observium Network Observation System Subject: Re: [Observium] Groups
This was one of my ideas too. Using groups to replace device type.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 15:54:15 "Pedersen, Sean" spedersen@io.com wrote:
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items – replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.orgmailto:adama@memetic.org>, Observium Network Observation System <observium@observium.orgmailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?) - Matching group in alert checkers - Access granting for users complementing the device-based ones - Alerting address/contact per group - ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote: The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.commailto:milton@valvesoftware.com> To: "observium@observium.org"mailto:observium@observium.org <observium@observium.orgmailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It would be terrific if billing is capable to use port group
On 12/11/2014 23:45, Marco Spicuglia wrote:
Some examples:
All devices of type X in the network
All devices in room Y
All devices of type X in datacentre Z.
All devices in the first cabinet of each cabinet row in the network
All ports used by customer XYZ
All network items ordered in 2014
You name it, it really depends on how good people are with setting up
their conventions.
I can already do all of the above filtering, thanks to your groups system.
However, tell me if I'm wrong, the filters and the search function are not looking for vlan details.
Some networks have thousands of vlans and it might be handy to have a search/grouping for that too.
Cheers,
Marco
*From:* observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org *Sent:* 12 November 2014 23:23 *To:* Observium Network Observation System *Subject:* Re: [Observium] Groups
This was one of my ideas too. Using groups to replace device type.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 15:54:15 "Pedersen, Sean" spedersen@io.com wrote:
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items – replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cx mailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.org mailto:adama@memetic.org>, Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?)
- Matching group in alert checkers
- Access granting for users complementing the device-based ones
- Alerting address/contact per group
- ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote:
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.com mailto:milton@valvesoftware.com> To: "observium@observium.org" <observium@observium.org mailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
observium mailing list observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
*Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.*
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That doesn't really make any sense :)
------ Original Message ------ From: "Robin Douine" robin.douine@arkena.com To: "Observium Network Observation System" observium@observium.org Sent: 11/19/2014 6:43:11 AM Subject: Re: [Observium] Groups
It would be terrific if billing is capable to use port group
On 12/11/2014 23:45, Marco Spicuglia wrote:
Some examples:
All devices of type X in the network
All devices in room Y
All devices of type X in datacentre Z.
All devices in the first cabinet of each cabinet row in the network
All ports used by customer XYZ
All network items ordered in 2014
You name it, it really depends on how good people are with setting
up their conventions.
I can already do all of the above filtering, thanks to your groups system.
However, tell me if I'm wrong, the filters and the search function are not looking for vlan details.
Some networks have thousands of vlans and it might be handy to have a search/grouping for that too.
Cheers,
Marco
*From:* observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org *Sent:* 12 November 2014 23:23 *To:* Observium Network Observation System *Subject:* Re: [Observium] Groups
This was one of my ideas too. Using groups to replace device type.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 15:54:15 "Pedersen, Sean" spedersen@io.com wrote:
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items – replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cx mailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.org mailto:adama@memetic.org>, Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?)
- Matching group in alert checkers
- Access granting for users complementing the device-based ones
- Alerting address/contact per group
- ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote:
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.com mailto:milton@valvesoftware.com> To: "observium@observium.org" <observium@observium.org mailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
observium mailing list
observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
*Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.*
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Robin DOUINE - Network Manager Arkena - http://www.arkena.com 27 Bd Hippolyte Marques, 94200 Ivry sur Seine, France Phone : +33.1.58.68.62.33 / Cell : +33.6.87.05.20.02 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Perhaps, I didn't explain myself properly. On the billing page, we have to insert billed port by billed port, it would be easier if the billed port would be inserted automatically based on regex. Like the groups/alerts or the aggregate graph system for peering and transit.
On 20/11/2014 23:53, Adam Armstrong wrote:
That doesn't really make any sense :)
------ Original Message ------ From: "Robin Douine" robin.douine@arkena.com To: "Observium Network Observation System" observium@observium.org Sent: 11/19/2014 6:43:11 AM Subject: Re: [Observium] Groups
It would be terrific if billing is capable to use port group
On 12/11/2014 23:45, Marco Spicuglia wrote:
Some examples:
All devices of type X in the network
All devices in room Y
All devices of type X in datacentre Z.
All devices in the first cabinet of each cabinet row in the network
All ports used by customer XYZ
All network items ordered in 2014
You name it, it really depends on how good people are with setting up
their conventions.
I can already do all of the above filtering, thanks to your groups system.
However, tell me if I'm wrong, the filters and the search function are not looking for vlan details.
Some networks have thousands of vlans and it might be handy to have a search/grouping for that too.
Cheers,
Marco
*From:* observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org *Sent:* 12 November 2014 23:23 *To:* Observium Network Observation System *Subject:* Re: [Observium] Groups
This was one of my ideas too. Using groups to replace device type.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 15:54:15 "Pedersen, Sean" spedersen@io.com wrote:
- Matching group in alert checkers
Oh my god, yes.
Another suggestion/nice-to-have would be the ability to group devices, ports, etc. and then generate menu items – replacing the interface description parser. Instead of writing a custom parser, you can just use the built-in matching functions that already exist for Alerts. Though the custom parser does leave some more room for more complicated regex.
From: Tom Laermans <tom.laermans@powersource.cx mailto:tom.laermans@powersource.cx> Reply-To: Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Date: Wednesday, November 12, 2014 at 2:46 PM To: Adam Armstrong <adama@memetic.org mailto:adama@memetic.org>, Observium Network Observation System <observium@observium.org mailto:observium@observium.org> Subject: Re: [Observium] Groups
Here are some pointers:
- Device dropdown (instead of types perhaps?)
- Matching group in alert checkers
- Access granting for users complementing the device-based ones
- Alerting address/contact per group
- ...
Yes, yes, I know... "get on it". :P
Tom
On 12/11/2014 22:15, Adam Armstrong wrote:
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.com mailto:milton@valvesoftware.com> To: "observium@observium.org" <observium@observium.org mailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
observium mailing list
observium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
*Founded in 2007, IO is a worldwide leader in software defined data center technology, services and solutions that enable businesses and governments to intelligently control their information.*
The communication contained in this e-mail is confidential and is intended only for the named recipient(s) and may contain information that is privileged, proprietary, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. Please immediately notify the sender of the error, and delete this communication including any attached files from your system. Thank you for your cooperation. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Robin DOUINE - Network Manager Arkena - http://www.arkena.com 27 Bd Hippolyte Marques, 94200 Ivry sur Seine, France Phone : +33.1.58.68.62.33 / Cell : +33.6.87.05.20.02 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I find the groups system very useful.
We use it constantly for quickly getting to the items we want, which are already categorised by naming convention.
Thank you so much for your quick wins Adam :)
________________________________ From: observium observium-bounces@observium.org on behalf of Adam Armstrong adama@memetic.org Sent: 12 November 2014 22:15 To: Observium Network Observation System Subject: Re: [Observium] Groups
The groups system exists simply because it was a relatively "quick win" by re-using the alerting system's association code. I'm not entirely sure what I would expect it to be used for. I didn't really get that far!
I had started adding group filtering abilities to the device and ports pages, which sort of does part of what you want, especially if it was expanded to other entity types.
Having fully customisable pages is still something I really have no idea how to do, but I think we *should* do, somehow.
adam.
------ Original Message ------ From: "Milton Ngan" <milton@valvesoftware.commailto:milton@valvesoftware.com> To: "observium@observium.org" <observium@observium.orgmailto:observium@observium.org> Sent: 11/11/2014 3:52:25 PM Subject: [Observium] Groups
What is the intention of the groups feature? It seems like a really powerful way to group stuff together and have interesting views of things. But right now it just generates a list of entities that you can click through or hover over. I took a look at the code that generates all the various graph layouts (iftypes, health, ports). It seems that every page has its own code for handling the graph layout. It seem like this would be a great place to leverage a bunch of the existing code so you can create group specific views of sensors, ports etc... But it doesn't look like the code is structured that way (i.e reusable components/widgets).
The standard views are good, but I want to be able to see them on a per datacenter/region basis rather than globally. The global view is visually interesting/pretty it is less useful.
participants (6)
-
Adam Armstrong -
Marco Spicuglia -
Milton Ngan -
Pedersen, Sean -
Robin Douine -
Tom Laermans