Azure
Installation
- Create a directory for the install. Suggested::
mkdir -p /opt/circonus/cloud-agent
- Download the latest release
- Unpack the release in the directory created in first step
- In this directory, create a config folder. Suggested:
mkdir /opt/circonus/cloud-agent/etc/azure.d
- Auto-create a service specific configuration template in the desired format (yaml, toml, or json). Suggested:
sbin/circonus-cloud-agentd --enable-azure --azure-example-conf=yaml > etc/azure.d/azure-config.yaml
.- Note, the
id
in the template is defaulted to the filename. This should be changed to a name that will be unique across all cloud-agents used in Circonus - Follow configuration instructions to finish config settings
- Note, the
- Setup as a system service or run in foreground ensuring that
--enable-azure
is specified
Options
$ sbin/circonus-cloud-agentd -h
The Circonus Cloud Agent collects metrics from cloud infrastructures and fowards them to Circonus.
Usage:
circonus-cloud-agent [flags]
Flags:
--azure-conf-dir string Azure configuration directory (default "/opt/circonus/cloud-agent/etc/azure.d")
--azure-example-conf string Show Azure config (json|toml|yaml) and exit
-c, --config string config file (default: circonus-cloud-agent.yaml|.json|.toml)
-d, --debug [ENV: CCA_DEBUG] Enable debug messages
--enable-azure Enable Azure metric collection client
-h, --help help for circonus-cloud-agent
--log-level string [ENV: CCA_LOG_LEVEL] Log level [(panic|fatal|error|warn|info|debug|disabled)] (default "info")
--log-pretty [ENV: CCA_LOG_PRETTY] Output formatted/colored log lines [ignored on windows]
-V, --version Show version and exit
Configuration
Setting up application in Azure
- Login to the Azure portal
- Create application
- Name the application (e.g.
circonus-cloud-agent
) - Add reader role to subscription for the application
- Name the application (e.g.
- Collect application configuration information
- Directory ID
- Application ID
- Application secret
- Subscription ID
- Add these to the
azure
section of the config file.
Circonus
- Use Circonus UI to create or identify an API Token to use
- Add the
key
to the config file under thecirconus
section
Azure configuration file settings
directory_id
applicaiton_id
application_secret
subscription_id
resource_filter
- Use the resourceFilter setting to limit the resources from which metrics are collected. Otherwise, ALL metrics from ALL resources will be collected. The suggested method would be to add a tag to each resource from which to collect metrics and use a filter expression such astagname eq 'circonus' and tagValue eq 'enabled'
cloud_name
- defaultAzurePublicCloud
user_agent
- defaultcirconus-cloud-agent
interval
- collection interval in minutes [>=default], default5
Example configuration
Minimum configuration:
---
id: ...
azure:
directory_id: ...
application_id: ...
application_secret: ...
subscription_id: ...
circonus:
key: ...