-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #210 from visulate/pgoldtho/backendConfig
Pgoldtho/backend config
- Loading branch information
Showing
5 changed files
with
123 additions
and
99 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
72 changes: 72 additions & 0 deletions
72
google-marketplace/chart/visulate-for-oracle/ubbagent-config.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
# The identity section contains authentication information used | ||
# by the agent. | ||
identities: | ||
- name: gcp | ||
gcp: | ||
# This parameter accepts a base64-encoded JSON service | ||
# account key. The value comes from the reporting secret. | ||
encodedServiceAccountKey: $AGENT_ENCODED_KEY | ||
|
||
# The metrics section defines the metric that will be reported. | ||
# Metric names should match verbatim the identifiers created | ||
# during pricing setup. | ||
metrics: | ||
- name: database_connections | ||
type: int | ||
metric_kind: DELTA | ||
value_type: INT64 | ||
unit: h | ||
|
||
# The endpoints section of a metric defines which endpoints the | ||
# metric data is sent to. | ||
endpoints: | ||
- name: on_disk | ||
- name: servicecontrol | ||
passthrough: {} | ||
|
||
- name: time | ||
type: int | ||
metric_kind: DELTA | ||
value_type: INT64 | ||
unit: h | ||
endpoints: | ||
- name: on_disk | ||
- name: servicecontrol | ||
|
||
# The passthrough marker indicates that no aggregation should | ||
# occur for this metric. Reports received are immediately sent | ||
# to the reporting endpoint. We use passthrough for the | ||
# instance_time metric since reports are generated | ||
# automatically by a heartbeat source defined in a later | ||
# section. | ||
passthrough: {} | ||
|
||
# The endpoints section defines where metering data is ultimately | ||
# sent. Currently supported endpoints include: | ||
# * disk - some directory on the local filesystem | ||
# * servicecontrol - Google Service Control | ||
endpoints: | ||
- name: on_disk | ||
# The disk endpoint is useful for debugging, but its inclusion | ||
# is not necessary in a production deployment. | ||
disk: | ||
reportDir: /var/lib/ubbagent/reports | ||
expireSeconds: 36000 | ||
- name: servicecontrol | ||
servicecontrol: | ||
identity: gcp | ||
# The service name is unique to your application and will be | ||
# provided during onboarding. | ||
serviceName: visulate-for-oracle.mp-visulate-llc-public.appspot.com | ||
consumerId: $AGENT_CONSUMER_ID # From the reporting secret. | ||
|
||
# The sources section lists metric data sources run by the agent | ||
# itself. The currently-supported source is 'heartbeat', which | ||
# sends a defined value to a metric at a defined interval. | ||
sources: | ||
- name: instance_time_heartbeat | ||
heartbeat: | ||
metric: time | ||
intervalSeconds: 3600 | ||
value: | ||
int64Value: 1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters