Service tabs

Properties

_images/doc_collector_svc_tabs.png

Property

Description

opensvc version

Pushed to database daily by the opensvc nodeware cronjob.

unackowledged errors

A count of the unacknowledged errors on this service found in the actions table.

type

Service type can be PRD, DEV, …

comment

Pushed to database daily by the opensvc nodeware cronjob. This information resides in the service env file on the nodes.

last update

Timestamp updated upon service information receive from the nodeware cronjob.

container name

Host Name of the virtual machine encapsulated in the service, if any.

container type

Virtualisation driver to handle the encapsulated virtual machine, if any.

responsibles

List of administrators contact names for this service.

responsibles mail

List of administrators contact emails for this service.

primary node

Host name of the node where the service should be running in optimal situation.

nodes

All nodes where the service may be running in degraded situation (not in disaster recovery situation).

drp node

Host name of the node the service should be running in a disaster recovery situation.

drp nodes

All nodes where the service may be running in disaster recovery situation.

status

Display the per-node synthetic service status.

Alerts

The dashboard table filtered to display only the service alerts.

Instances Status

The service instances table filtered to display only the service instances.

Resources Status

The resource status table filtered to display only the service resources.

Resources Info

The resource info table filtered to display only the service resources.

Actions

The service actions table filtered to display only the service actions.

Logs

The logs table filtered to display only the service entries.

Config

_images/collector.tabs.service.config.png

Display the service configuration file pushed by the agent in an online editor. Any change made in the configuration file is not pushed to the node running the service. In order to propagate changes to the node, the service configuration file must be pulled from the node. Without pulling the service, the configuration change in the collector would be overwritten by the live configuration running on the node at next agent service configuration push.

Topology

A diagram of apps, resources, service, nodes, storage, locations relations.

_images/doc_collector_svc_tabs_topo.png

Startup

_images/collector.tabs.service.startup.png

A diagram of the service startup sequence, highlighting parallel and sequential steps.

Storage

Display:

  • The service node-to-array cabling through the SAN

  • A table of the nodes host bus adapter information

  • A table of the nodes host bus adapter-to-target ports information, with used SAN views

  • A table of the service disks, with their information parsed from storage arrays

Container stats

Performance statistics of the container resources of the service.

Stats

_images/collector.tabs.service.stats.png

Performance statistics of the nodes hosting the service.

Wiki

_images/collector.tabs.service.wiki.png

A wiki page the service responsibles can use to share information about the service.

Avail

_images/collector.tabs.service.avail.png

A timeline of service instances and resources state changes.

Pkgdiff

_images/collector.tabs.service.pkgdiff.png

A comparison of installed packages differences between nodes hosting the service.

Compliance

_images/collector.tabs.service.compliance.png

Displays:

  • The current per-module compliance status of the service

  • The service rulesets and modulesets attachments

  • Compliance alerts details