You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 16, 2023. It is now read-only.
Merge pull request #21 in DEV/k8s-argus from DEV-41301-upgrade-the-go-sdk-to-v2 to develop
* commit '69f8fb54b9df0a573f1415bcbb99070779cd975d': (21 commits)
DEV-41301 Upgrade the go sdk to v2
DEV-41301 Upgrade the go sdk to v2
DEV-41301 Upgrade the go sdk to v2
DEV-41301 Upgrade the go sdk to v2
DEV-41301 Upgrade the go sdk to v2
DEV-48974 Upgrade the go version of the argus from 1.9 to 1.11 (#104)
DEV-48974 Upgrade Argus from golang 1.9 to 1.11
Develop (#103)
Dev 49046 fix the internal ip cannot found (#102)
Update node_test.go
Develop (#99)
Dev 42060 improve the initSync and the branch of the lm sdk (#98)
remove beta tag (#96)
Remove beta tag (#97)
Develop (#95)
bump version
Dev-40217 support to set log levels and improve (#94)
Dev-40217 support to set log levels and improve
Stash to GitHub (#92)
Updating docs & readme (#91)
...
> **Note:** Argus is a community driven project in an alpha state. LogicMonitor support will not be able to assist with any issues related to Argus.
16
-
17
-
**Argus** is a tool for monitoring Kubernetes with [LogicMonitor](https://www.logicmonitor.com). Some of the key features of Argus are:
18
-
-**Automated Device Group Management:** Leverages Kubernetes events to provide real-time accuracy of a cluster's resources in LogicMonitor, and organizes them by resource type and namespace in the [Device Tree](https://www.logicmonitor.com/support/devices/devices-page-overview/navigating-devices/).
19
-
-**Automated Device Management:** Discovers etcd members, cluster nodes, services, and pods, and automates the management of their lifecycle as [Devices](https://www.logicmonitor.com/support/devices/) in LogicMonitor.
20
-
-**Automated Device Property Management:** Discovers Kubernetes resource metadata and maps them to [Device Properties](https://www.logicmonitor.com/support/devices/adding-managing-devices/device-properties/).
15
+
**Argus** is a tool for monitoring Kubernetes with
16
+
[LogicMonitor](https://www.logicmonitor.com). Some of the key features of Argus
17
+
are:
18
+
-**Automated Resource Discovery:** Leverages Kubernetes events and
19
+
LogicMonitor's API to provide real-time accuracy of a cluster's resources in
20
+
LogicMonitor. Discovers etcd members, cluster Nodes, Services, and Pods, and
21
+
automates the management of their lifecycle as
22
+
[Resources](https://www.logicmonitor.com/support/devices/) in LogicMonitor.
23
+
-**Comprehensive Monitoring:** Dockerized LogicMonitor Collectors running in a
24
+
Stateful Set and managed by Argus collect data via the Kubernetes API for Nodes,
25
+
Pods, Services, and Containers. Additionally, you can leverage LogicMonitor
26
+
DataSources to monitor your applications running within the cluster.
21
27
22
28
See the [documentation](https://logicmonitor.github.io/k8s-argus) to discover more about Argus.
Copy file name to clipboardExpand all lines: docs/argus/index.html
+7-8Lines changed: 7 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -338,14 +338,13 @@
338
338
<divclass="wrapper">
339
339
<h1>Argus </h1>
340
340
341
-
<divclass="admonition warning">
342
-
<pclass="admonition-title">Warning</p>
343
-
<p>Argus is a community driven project in an alpha state. LogicMonitor support will not be able to assist with any issues related to Argus.</p>
344
-
</div>
345
-
346
-
<hr/>
347
-
348
-
<p>Argus is a tool that helps users of <ahref="https://www.logicmonitor.com">LogicMonitor</a> keep up with the highly dynamic topology of a Kubernetes cluster.</p>
341
+
<p>Argus is a tool that helps users of <ahref="https://www.logicmonitor.com">LogicMonitor</a>
342
+
keep up with the highly dynamic nature of a Kubernetes cluster. Argus runs as a
343
+
Pod in your cluster, and uses LogicMonitor’s API to add Nodes, Pods, and
344
+
Services into monitoring. Once in monitoring, data collection starts
345
+
automatically. Data is collected for Nodes, Pods, Containers, and Services via
346
+
the Kubernetes API. Additionally, you can leverage LogicMonitor DataSources to
347
+
monitor your applications running within the cluster.</p>
349
348
350
349
<!-- __*"And the goddess stirred in him unwearying strength: sleep never fell upon his eyes; but he kept sure watch always."*__
Argus is a community driven project in an alpha state. LogicMonitor support will not be able to assist with any issues related to Argus.
22
-
Argus is a tool that helps users of LogicMonitor keep up with the highly dynamic topology of a Kubernetes cluster.</description>
20
+
<description>Argus is a tool that helps users of LogicMonitor keep up with the highly dynamic nature of a Kubernetes cluster. Argus runs as a Pod in your cluster, and uses LogicMonitor&rsquo;s API to add Nodes, Pods, and Services into monitoring. Once in monitoring, data collection starts automatically. Data is collected for Nodes, Pods, Containers, and Services via the Kubernetes API. Additionally, you can leverage LogicMonitor DataSources to monitor your applications running within the cluster.</description>
<li><strong>imageRepository (default: <code>"logicmonitor/collectorset-controller"</code>):</strong> The respository to use for the collectorset-controller docker image.</li>
363
-
<li><strong>imageTag:</strong> The collectorset-controller image tag to use.</li>
364
+
<li><strong>imageRepository (default: <code>"logicmonitor/collectorset-controller"</code>):</strong> The
365
+
respository to use for the collectorset-controller docker image.</li>
366
+
<li><strong>imageTag:</strong> The collectorset-controller <ahref="https://hub.docker.com/r/logicmonitor/collectorset-controller/tags/">image tag</a> to use.</li>
364
367
</ul>
365
368
366
369
<h1id="configuring-argus-via-the-helm-chart">Configuring Argus via the Helm Chart</h1>
@@ -375,29 +378,39 @@ <h1 id="configuring-argus-via-the-helm-chart">Configuring Argus via the Helm Cha
375
378
<li><strong>account:</strong> The LogicMonitor account name.</li>
376
379
<li><strong>clusterName:</strong> A unique name given to the cluster’s device group.</li>
377
380
<li><strong>collector.replicas:</strong> The number of collectors to create and use with Argus.</li>
378
-
<li><strong>collector.size:</strong> The collector size to install. Can be nano, small, medium, or large.</li>
381
+
<li><strong>collector.size:</strong> The collector size to install. Can be nano, small, medium,
<li><strong>deleteDevices (default: <code>true</code>):</strong> On a delete event, either delete from LogicMonitor or move the device to the <code>_delted</code> device group.</li>
389
+
<li><strong>deleteDevices (default: <code>true</code>):</strong> On a delete event, either delete from
390
+
LogicMonitor or move the device to the <code>_delted</code> device group.</li>
386
391
<li><strong>disableAlerting (default: <code>false</code>):</strong> Disable alerting for all devices added.</li>
<p>In most applications there are generally two types of configuration options available. Options that do not contain sensitive information, and options that do contain sensitive information. Argus retrieves its’ configuration from two different sources for each of these types.</p>
404
+
<p>In most applications there are generally two types of configuration options
405
+
available. Options that do not contain sensitive information, and options that
406
+
do contain sensitive information. Argus retrieves its’ configuration from two
407
+
different sources for each of these types.</p>
397
408
398
-
<p>For non-sensitive configuration options, Arugs will read from a file on disk. For sensitive information, Arugs will read from environment variables.</p>
409
+
<p>For non-sensitive configuration options, Argus will read from a file on disk.
410
+
For sensitive information, Argus will read from environment variables.</p>
399
411
400
-
<p>To configure the non-sensitive information, create a YAML file located at <code>/etc/argus/config.yaml</code>. Here is an example file you can modify to your needs:</p>
412
+
<p>To configure the non-sensitive information, create a YAML file located at
413
+
<code>/etc/argus/config.yaml</code>. Here is an example file you can modify to your needs:</p>
<description>Configuring the Collecorset Controller via the Helm Chart The Collectorset controller Helm chart supports the fololowing values:
40
+
<description>Configuring the Collectorset Controller via the Helm Chart The Collectorset controller Helm chart supports the following values:
41
41
Required Values:
42
42
accessID: The LogicMonitor API key ID. accessKey: The LogicMonitor API key. account: The LogicMonitor account name. clusterName: A unique name given to the cluster&rsquo;s device group. Optional Values:
43
-
enableRBAC (default: true): Enable RBAC. etcdDiscoveryToken: The public etcd discovery token used to add etcd hosts to the cluster device group.</description>
43
+
enableRBAC (default: true): Enable RBAC. If your cluster does not have RBAC enabled, this value should be set to false.</description>
Copy file name to clipboardExpand all lines: docs/getting-started/index.html
+9-5Lines changed: 9 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -346,15 +346,14 @@ <h1>Getting Started </h1>
346
346
<p>The simplest way to get started with Argus is to install it using <ahref="https://github.com/kubernetes/helm">Helm</a>. Prior to installation, you will need a
0 commit comments