Correct one SQL DB instance with low CPU utilization

SQL instances can be costly to run, especially if they're rarely used, instances with low average CPU utilization should be reviewed to determine if they're still required.

This pipeline allows you to specify a single instance and then either send a notification or attempt to perform a predefined corrective action.

Whilst it is possible to utilise this pipeline standalone, it is usually called from the correct_sql_db_instances_with_low_cpu_utilization pipeline.

Run the pipeline

To run this pipeline from your terminal:

flowpipe pipeline run gcp_thrifty.pipeline.correct_one_sql_db_instance_with_low_cpu_utilization \
  --arg 'instance_name=<string>' \
  --arg 'title=<string>' \
  --arg 'project=<string>' \
  --arg 'cred=<string>'

Use this pipeline

To call this pipeline from your pipeline, use a step:

step "pipeline" "step_name" {
  pipeline = gcp_thrifty.pipeline.correct_one_sql_db_instance_with_low_cpu_utilization  
  args = {
    instance_name = <string>
    title = <string>
    project = <string>
    cred = <string>
  }
}

Params

Name	Type	Required	Description	Default
instance_name	string	Yes	The name of the SQL DB instance.	-
title	string	Yes	Title of the resource, to be used as a display name.	-
project	string	Yes	GCP Project ID of the resource(s).	-
cred	string	Yes	Name of the credential to be used for any authenticated actions.	-
notifier	string	Yes	The name of the notifier to use for sending notification messages.	`default`
notification_level	string	Yes	The verbosity level of notification messages to send. Valid options are 'verbose', 'info', 'error'.	`info`
approvers	list(string)	Yes	List of notifiers to be used for obtaining action/approval decisions.	`[ "default" ]`
default_action	string	Yes	The default action to use for the detected item, used if no input is provided.	`notify`
enabled_actions	list(string)	Yes	The list of enabled actions to provide to approvers for selection.	`[ "skip", "stop_sql_instance", "delete_instance" ]`

Outputs

This pipeline has no outputs.

Correct one SQL DB instance with low CPU utilization

Run the pipeline

Use this pipeline

Params

Outputs

Tags