Page Comparison

...

For more information, see proxy on the CLI reference page.

3.

...

AGILITY is upgraded periodically as new features and functionality become available. Similarly, new AGILITY models can be activated by installing one or more sub-components of AGILITY. For this purpose, AGILITY needs to communicate with B-Yond’s artifact repository (currently hosted on Oracle Ashburn cloud).

To facilitate this communication, B-Yond will provide you with registry name, and credentials (username, password). Use the following command to enable the communication with B-Yond artifact registry.

 agility global registry --name "iad.ocir.io" --username "username" --password "password" 

For this command there is no reset, you can simply re-enter the information if you make a mistake or you want to make an update.

For more information, see global on the CLI reference page.

4. Set up AGILITY context

AGILITY is personalized for your environment with the models that are specifically created for your use cases. The base version of AGILITY is our Community edition which contains standards models but is missing your environment-related information such as possible host files, protocol/port mappings, etc. In order to customize AGILITY for optimal performance, we will provide you with a context(-string) that needs to be entered via the following command.

agility context --name "context-string"

For this command there is no reset, you can simply re-enter the information to make an update.

For more information, see context on the CLI reference page.

...

Setup AGILITY License

1. Backup the current B-Yond License

   Code Block
   kubectl --namespace agility get secret agility-operator -o yaml > /<safe-directory-path>/secret-byond-license.yaml

2. Store the new B-Yond License on a temporary directory

   Code Block
   export BYOND_LICENSE_PATH="/tmp/license.token" vi ${BYOND_LICENSE_PATH}

3. Create the new B-Yond license kubernetes secret locally:

   Code Block
   kubectl --namespace agility create secret generic agility-operator \ --from-file="license.token"=${BYOND_LICENSE_PATH} --dry-run=client -o yaml > ${BYOND_LICENSE_PATH}.yaml

4. Replace the B-Yond license kubernetes secret:

   Code Block
   kubectl --namespace agility replace -f ${BYOND_LICENSE_PATH}.yaml

5. Restart AGILITY Operator instance

   Code Block
   kubectl -n agility scale deploy/agility-operator --replicas 0 && kubectl -n agility scale deploy/agility-operator --replicas 1

4. Install AGILITY-Monitoring

AGILITY comes with a set of tools that are used for collecting performance metrics, logs, and traces which can be displayed in dashboards and can generate alarms and notifications. AGILITY-Monitoring is based on Grafana software stack, specifically Grafana, Prometheus, Loki, and Tempo. If the AGILITY is installed as a VM, you can enable AGILITY-Monitoring with a single command.

...

For more information, see monitoring on the CLI reference page.

...

5. Enable telemetry remote

This is enabled by default on new deployments. AGILITY forwards the metrics, logs, and traces to B-Yond’s central monitoring server (central-monitoring.b-yond.com:4317). This is essential for B-Yond to fulfill its SLA commitments to its customers. To interact with remote monitoring, use the following command.

...

For more information, see telemetry on the CLI reference page.

...

6. Enable telemetry local

AGILITY forwards the metrics, logs, and traces to the local AGILITY-Monitoring that was activated in step 6. This is activated by a command similar to the one we used for enabling remote telemetry.

...

...

Set up pipeline (optional)

Use the settings in the AGILITY UI to set up and manage your ingestion pipelines..

Add AGILITY API (optional)

Use the AGILITY API to analyze network traces