unable to find collector about k8s-helm-charts HOT 5 CLOSED

For anyone else that find this, @woz5999 was correct. We did have not an escalating_chain_id of 1.

RIght now you can find your chain_id with a python script supplied by LM but they have made a feature request for it to appear in the UI.

You can then add the value to the install command like so

--collectorEscalatingChainID='6' \

thanks

from k8s-helm-charts.

Hi @jurgenweber. Can you try setting the collectorVersion flag? Currently the Helm chart sets a default, but this might need to be required upon installation of the chart. Also, I might be able to help you faster in the gitter room: https://gitter.im/k8s-argus/Lobby

from k8s-helm-charts.

I think I missed you but I tried:

helm upgrade \
  --install \
  --debug \
  --wait \
  --namespace kube-monitoring \
  --set accessID='sdfg' \
  --set accessKey='sdfg' \
  --set account='example' \
  --set clusterName='example.com.au' \
  --set collectorDescription='Collector Description' \
  --set collectorVersion='24216' \
  --set etcdDiscoveryToken='etcd-cluster-token-etcd' \
  argus logicmonitor/argus

with the same result.

from k8s-helm-charts.

I wasn't sure if this was to obfuscate your account info:

  --set account='example' \

A LogicMonitor account is required to use Argus.

from k8s-helm-charts.

@jurgenweber Looking at the logs, I'm wondering if maybe the default escalation chain has been removed from your account. If you don't specify the configuration "escalating_chain_id", the container wrapper assumes the default chain id of 1. Based on these logs and that error code, I suspect that your account no longer has an escalation chain with id 1. Try setting that configuration item to a valid escalation chain id.

from k8s-helm-charts.