- URL/IP of the SixthSense collector (your tenant URL, which will be provided by the onboarding team).
- Access token from the SixthSense portal (See Get Access token from SixthSense portal section).
- PACKAGE_TOKEN (will be provided by the onboarding team).
Downloading the agent
Download the SixthSense agent into your project dependencies "@sixthsense/sixthsense-de-agent": "^1.0.3" (Add this dependency to the package.json file of your application).
Configuring the agent
Agent configurations will be added to the entry point of your application.
|Name of the application
|tenant URL which will be provided by the Customer Support team
|Get the access token from the SixthSense portal
Add sixthsense-de.js plugin
Geting Access token from the SixthSense portal
- Login to the SixthSense portal.
- Navigate to Settings on the left pane.
- Navigate to Access token.
- Click Show access token.
- Click Copy to copy the access token and add it to the token_from_ui.
Running your application
Run the following commands before the npm install command one by one.
- PACKAGE_TOKEN (will be provided by the onboarding team.)
- Run npm install command to download all the dependencies (npm i @sixthsense/sixthsense-de-agent)
- Run the start command to run your application.
Agent Integrations in a Docker
Adding the Dependency Download configuration in a Docker file
- The SixthSense agent is hosted on the Rakuten self-hosted private Package manager. To download the package, an additional step is required for authentication.
- Add the below code snippet in your docker file before the NPM install command as follows:
- This will set the configuration to identify the SixthSense package registry and also tells the dependency to download from the URL that you defined with the same name in the package.json file.
- https://artifacts-observability.sixthsense.rakuten.com/api/v4/projects/9/packages/npm/. This is the SixthSense package manager URL
- _authToken' "PACKAGE_TOKEN"– Since the package is hosted in a private package manager it requires authentication to identify the user. This auth token will be defined during your onboarding.
- For simplicity, the auth token is placed in the docker file. However, if you don’t wish to add it in the docker file and push it to your version control repository, you can pass this auth token based on your credential management by setting the environment variable and passing the secrets from Jenkins CI/CD, and so on.
- Now build your application with docker build and run the docker image/container. The agent is integrated with your application and you will start seeing the metrics in the SixthSense dashboard.
Pass the PACKAGE_TOKEN as build arguments.
Example: Docker Configuration