Platform

One agent. The commands the repository ships.

Linux, Windows, Docker, Helm, OpenShift, Ansible, and Terraform. Replace INGEST_KEY. The endpoint in these lines is the public demo.

The lines are copied from the install scripts, the downloads catalog, and deploy/integrations. They were not invented for this page. Films of the same installs are on the docs page.

tar -xzf onemonvue-agent-0.9.0-linux-x86_64.tar.gz && cd onemonvue-agent-0.9.0-amd64 && sudo ./install.sh --unattended --endpoint 'https://lucitrace.onrender.com' --tenant nonprod --key 'INGEST_KEY' --metadata 'AppID=000431' --metadata 'BU=Payments'

The downloads catalog command. The archive is served at /install/releases/ on a running server. Logs default to now. The agent file in this repository is a shell stub.

powershell -ExecutionPolicy Bypass -File .\install.ps1 -Unattended -Endpoint 'https://lucitrace.onrender.com' -Tenant nonprod -Key 'INGEST_KEY' -Metadata 'AppID=000431','BU=Payments'

Service name OneMonVueAgent. The zip README says the exe was not compiled and an MSI was not compiled. These steps were not run on Windows from this repo.

docker build -t onemonvue/agent:0.9.0 -f Dockerfile . && docker run -d --name onemonvue-agent --restart unless-stopped -e ONEMONVUE_ENDPOINT='https://lucitrace.onrender.com' -e ONEMONVUE_TENANT=nonprod -e ONEMONVUE_KEY='INGEST_KEY' -e ONEMONVUE_TAGS='team=payments' -v onemonvue-logs:/var/log/onemonvue onemonvue/agent:0.9.0

Run the build from server/agent/install, where the Dockerfile copies the agent. The image was not pushed. The run flags are the ones the install page builds.

helm upgrade --install onemonvue onemonvue-agent-0.9.0.tgz --set tenant=nonprod --set endpoint=https://lucitrace.onrender.com --set tags=team=payments

Release name onemonvue. Chart version 0.9.0 ships a DaemonSet. This chart was not installed on a cluster from this repository. Add --set key=… if the agent should carry an ingest key.

helm upgrade --install onemonvue onemonvue-agent-0.9.0.tgz --set tenant=nonprod --set endpoint=https://lucitrace.onrender.com --set tags=team=payments

OpenShift runs the same chart. This repo has no operator, no SecurityContextConstraints file, and no oc install command. The only OpenShift manifest is the lab route at infra/k8s/openshift/route.yaml, and it is not the agent.

ansible-playbook playbook.yml

From deploy/integrations/ansible. The role calls install.sh with the same flags. The inventory needs a group named agents. This playbook was not run against a real inventory.

terraform plan -var 'create_kubernetes=true'

From deploy/integrations/terraform. create_aws, create_azure, create_gcp, and create_kubernetes default to false, so a plan creates nothing until you opt in. This module was not applied.

Kubernetes and OpenShift

The board in the demo is Kubernetes and OpenShift. The cluster prod-eu-1 is OpenShift 4.16.12, and the checkout pod is part of the same incident. OpenShift uses the same Helm chart. This repository has no operator, no SecurityContextConstraints file, and no oc install command. The only OpenShift manifest is the lab route, and it is not the agent.

What the agent file is

The agent file in the repository is a shell stub. It writes a line and sleeps. The install scripts, the chart, and the service names are what the product serves. A real collector replaces that file.

The same app runs with docker compose up, or on Fly. The agent command does not change. You hold the data directory when you run it.