The collector is commercially licensed web 2.0 site available either in SaaS mode or in client-hosted mode. Contact firstname.lastname@example.org for licensing information.
The collector centralizes the agents data and provides advanced filtering, reporting and accounting features.
Internet collector account configuration¶
Account registration the SaaS collector at https://collector.opensvc.com is open to all.
A newly created account has no privilege to see other users services. You have to ask email@example.com to add filters to your account so you can see your data. Filtering is based on domainnames patterns. You can declare as many domains as you need. The email address you setup during registration is important : it is used by the collector alarming subsystem as a mail sink for services you are responsible of.
Views present data as tables.
Each view has:
- A persistent filters selector
- A column selector
- A column filters bar
- A pager
- A csv export tool
- View-specific tools
The active filter is stored in database and applied on all collector views. It persists across navigation sessions. Upon filter selection, the view is reloaded.
Filters can be designed from theview.
View columns can be toggled on and off from the column selector. Each view has a default set of column displayed. User column selection is stored in database, thus persistent across user sessions and different browsing devices.
Column filters bar¶
Each column of the table supports filtering. Filters are applied upon
<enter> in any filter box. Filter box expressions are AND'ed. Filter syntax supports :
- Multiple character wildcard for SQL expressions. Can be used as a header, trailer or in the middle of a pattern (%gie%01%)
- Single character wildcard for SQL expressions. Can be used as a header, trailer or in the middle of a pattern (%gie%01%)
- AND multiple patterns (%gie%&%adomain.com)
- OR multiple patterns (%gie%|%adomain.com)
- Negate the pattern (!%gie%&%adomain.com)
- Select only empty cells (!empty)
- Select only cells with value superior to specified value or date (>2012-04-01)
- Select only cells with value inforior to specified value or date (<2012-04-01)
- Select only cells with value superior or equal to specified value or date (>=2012-04-01)
- Select only cells with value inforior or equal to specified value or date (<=2012-04-01)
In all views, clicking on a service name will open the service tabs to display the most comprehensive data set the collector knows about this service.
Pushed to database daily by the opensvc nodeware cronjob.
A count of the unacknowledged errors on this service found in the actions table.
Service type can be PRD, DEV, ...
Pushed to database daily by the opensvc nodeware cronjob. This information resides in the service env file on the nodes.
Timestamp updated upon service information receive from the nodeware cronjob.
Host Name of the virtual machine encapsulated in the service, if any.
Virtualisation driver to handle the encapsulated virtual machine, if any.
List of administrators contact names for this service.
List of administrators contact emails for this service.
Host name of the node where the service should be running in optimal situation.
All nodes where the service may be running in degraded situation (not in disaster recovery situation).
Host name of the node the service should be running in a disaster recovery situation.
All nodes where the service may be running in disaster recovery situation.
Display the per-node synthetic service status.
Display the per-node per-resource detailled service status.
Display the raw service configuration file pushed by the nodeware.
Sketches service-nodes-storage-sites relationships
In all views, clicking on a node name will open the node tabs to display the most comprehensive data set the collector knows about this node. server, os, mem, cpu, location, power
Information displayed in these tabs are extracted from the asset table. Assets can be loaded from a tiers enterprise asset manager or filled-in manually.
Generate and display graphs of performance metrics on the user-selected time range. The metrics are gathered daily from tools like glance and sar running on the nodes. The opensvc agent pushes this information to database.
Metrics collection depend on the operating system. Some of them are:
- cpu: usr, sys, wait, irq, guest, steal, idle, nice, iowait, soft
- mem: commit, free, used by usr, buffer, cache, sys
- swap: free, used, used but cached
- load: avg1, avg5, avg15, runq size, proc list size
- all-disks: io/s, bandwidth
- per-disk: io/s, request size, wait time, service time, %util, bandwidth
- The current node ruleset
- The current per-module compliance status of the node
- The modulesets attached to the node
A per-node wiki page the team responsible member can use to share information relative to the node.