OpsClarity Tags

 

OpsClarity Split Tags

The OpsClarity Split tag is used to separate hosts that are running the same service but shouldn’t be clustered together. A separate service object is created in the UI for each distinct tag.

Splitting services can make the topology more logical by identifying different pods of the same service and showing the connections between them. Another benefit of splitting services is that you can create specific monitors and alerts (with different thresholds) for each split service.

You can use any combination of the tags that you like, and both aren’t required to make a split.

There are two tags that OpsClarity uses to split services:

  • opsclarity_env
  • opsclarity_split

Adding OpsClarity Split Tags On AWS

You can add tags to your EC2 instances as shown below. In this case, the _env tag was used to separate staging from production, and the _split tag was used to break out different pods.

 

Example:

 

Adding OpsClarity Split Tags On The Host

Each agent can read tags via a YAML-formatted “opsclarity.conf” file. This file can be added in either /etc/opsclarity.conf or /opt/opsclarity/agent/etc/opsclarity.conf.

Example:

[root@kafka-prod1 etc]# cat opsclarity.conf

tags: 
  opsclarity_env: prod
  opsclarity_split: pod-a 

 

Service Example 

HOST REGION

SPLIT TAGS

BASE SERVICE OPSCLARITY SERVICE
Host-F us-east-1

opsclarity_split: cluster-X

opsclarity_env: prod

Mongo Mongo-cluster-X
Host-E us-east-1

opsclarity_split: cluster-X

opsclarity_env: staging

Mongo Mongo-cluster-X
Host-D us-east-1

opsclarity_split: cluster-X

Mongo Mongo-cluster-X
Host-C us-east-1 opsclarity_split: cluster-X Mongo Mongo-cluster-X
Host-B us-east-1 opsclarity_split: cluster-Z Mongo Mongo-cluster-Z
Host-A     Mongo (process: mongod) Mongo-Host-A
      Logstash Logstash-Host-A
      Logstash Logstash-cluster-Z
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.