Add terms to Glossary

Description

As part of SparkJam, Brean and I collected a list of terms to add to the Glossary. Items that are crossed out have been added to the glossary.

 

  • Flows 

  • Citius 

  • CircleCI 

  • Discourse 

  • Snaps 

  • Azure (Microsoft cloud hosting service) 

  • Kibana 

  • Docker 

  • Grafana (Graphical front end, also a competitor to ONMS) 

  • Kubernetes (For containerized applications) 

  • AKS (Microsoft Azure Kubernetes Service) 

  • Jira (Software issues, feature requests, IT requests – used by Nant and ONMS) 

  • Location 

  • Instance 

  • NOC 

  • Alarms 

  • Events 

  • Notifications 

  • Traps 

  • OaaS/OZ 

  • Daemon 

  • Availability 

  • Observability 

  • Topology 

  • RMI 

  • Telemetry 

  • auto-discovered nodes vs directed-discovered nodes vs new suspect on trap provisioned nodes vs new suspect on syslog provisioned nodes 

  • MOM 

  • Service 

  • Resource 

  • Sample

  • LDAP(S)

  • SNMP

  • SMTP

  • BSF

  • JMX

  • Northbounder

  • Southbounder

  • BSM

  • Drools Rules

  • Assets

  • MetaData

  • Categories (or Surveillance Categories)

  • Outages (vs. Alarms)

  • MIB

  • UEI

  • ISO Certs

Also received these comments re: terminology:

Replace “Provisioning Group”  with “Requisition"

“Node Category” and “Surveillance Category” are also synonyms. We should standardize on one (“Node Category”, though it really should be “Node Tag” to describe the function and behavior).

Batch #1:

  • Horizon 

  • Meridian 

  • Minion 

  • Sentinel 

  • ALEC 

  • HELM 

  • Dominion 

  • NEWTS 

  • NEPHRON 

  • TSS or TSDB (Time Series db) 

  • Kafka (Messaging service) 

  • ActiveMQ

  • Okta

  • Elasticsearch 

  • Cassandra 

  • Time series 

  • PostgreSQL 

  • APM – application perspective monitoring 

  • Round robin database 

  • IFTTT 

  • Requisitions 

  • Foreign-Source 

  • KSC

 

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Bonnie Robinson June 2, 2022 at 3:29 PM

Opened other issues to chunk out the glossary work and make it more manageable.

Bonnie Robinson June 2, 2022 at 3:15 PM
Edited

Just saw your question. We would have to write our own text. Unless the existing internet text is specifically designated as not under copyright, we would be in violation of copyright law. However, we can certainly base what we write off of text on the internet. Some things like protocols would have pretty limited definitions so it would be difficult to write something entirely unique.

Marcel Fuhrmann May 24, 2022 at 7:41 PM

I would like to collect some explanations for the lists above. Do we have to write our own text for the descriptions or can copy text from the internet?

Bonnie Robinson November 1, 2021 at 2:56 PM

Reopening to do second round of glossary.

Bonnie Robinson November 1, 2021 at 2:55 PM

First batch merged. Will reopen for second round.

Accepted

Details

Assignee

Reporter

Doc Backlog Status

Components

Sprint

Affects versions

Priority

PagerDuty

Created October 22, 2021 at 8:55 PM
Updated June 2, 2022 at 3:29 PM
Resolved June 2, 2022 at 3:29 PM