This email tf-cloud@hashicorp.support provides support with Terraform Cloud related issues only.
For Terraform OSS related questions, use cases and best practices, please check the Terraform community for assistance: https://www.terraform.io/
Our support engineers frequent the Terraform community forum and would be able to share some guidance there: https://discuss.hashicorp.com/
(from a question sent to hashicorp zendesk )
an old post found back on disqr about rsync (original date : circa 2016)
You might want to use the rsync exclude options directly in your script either by specifying a file with all the exclusions to perform, or by specifying them in the command line directly :
--exclude-from <file-name with 1 pattern by line>
--exclude <file or="" dir="">
For example :
One important thing to keep in mind when excluding a directory is that rsync will always consider the path to be relative to the source directory.
This can be used for example when you want to push your production from a Production JIRA instance to a Staging JIRA instance, but your dbconfig.xml is different (different DB auth parameters for example), and hence want to avoid some files.
Know where/if a plugin is used. Both have to be adapted to match a specific plugin.
First version gives more data but requires ScriptRunner.
Second version only uses SQL, but is less extensive.
You need to know what you're looking for : com.innovalog.jmwe.jira-misc-workflow-extensions
Adapted from : https://answers.atlassian.com/questions/205094/how-to-find-all-workflows-which-are-using-postfunctions-of-a-plugin
import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.workflow.JiraWorkflowimport com.atlassian.jira.workflow.WorkflowManagerimport java.util.regex.Matcher String searchText = 'com.innovalog.jmwe.jira-misc-workflow-extensions' WorkflowManager workflowManager = ComponentAccessor.getWorkflowManager()Collection<JiraWorkflow> workflows = workflowManager.getWorkflows() String result = "Workflow;Function;Type;Action;Step\r\n<br/>" workflows.each{workflow -> def workflowXml = workflow.descriptor.asXML() Matcher m = workflowXml =~ /${searchText}/ if (m.find()) { String workflow_name = "${workflow.name}${if(!workflow.isActive()){";(inactive)"} else ';active'}${if(workflow.isDraftWorkflow()){"(draft)"} else ''}" def wf = new XmlParser().parseText(workflowXml) List<Node> wf_flat = wf.depthFirst() wf_flat.each{ if (it.text() ==~ /.*${searchText}.*/){ result += "$workflow_name;${getNodeInfo(it,searchText)}\n\n<br/>" } } }}result String getNodeInfo(Node n, String search) { String nodetext = '' nodetext += "${n.text() - search}" def p = n.parent() while (p) { switch (p.name()) { case '"post-functions"': nodetext += ";post-function "; break case 'validators': nodetext += ";validator "; break case 'conditions': nodetext += ";condition "; break case 'action': nodetext += ";${p.attribute('name')} (${p.attribute('id')})"; break case 'step': nodetext += ";${p.attribute('name')} (${p.attribute('id')})"; break case 'global-actions': nodetext += ";GLOBAL "; break case 'initial-actions': nodetext += ";INITIAL "; break } p = p.parent() } return nodetext} |
SELECT workflowscheme.name, workflowschemeentity.scheme, issuetype.pname, workflowschemeentity.issuetypeFROM issuetype, workflowschemeentity, workflowschemeWHEREissuetype.id = workflowschemeentity.issuetype andworkflowscheme.id = workflowschemeentity.scheme and workflowschemeentity.workflow in (SELECT jiraworkflows.workflowname FROM jiraworkflows WHERE jiraworkflows.descriptor like '%com.company.plugin%'); |
(src = https://www.loggly.com/blog/performance-monitoring-aws-cloudwatch-metrics/ )
Step 1. Installing and Running Stress-ng
Stress-ng
is a load simulator available for the Ubuntu operating system. The
utility has a wide variety of command line switches used for customizing
the load. The installation is fairly simple as well:
# apt-get install stress-ng
More details about stress-ng can be found on the Ubuntu man page.
Once the tool is installed, it can be run as a command to simulate a CPU load with the following:
4 worker threads
80% load
Timeout after 25 minutes (1,500 seconds)
# stress-ng --timeout 1500 --cpu 4 --cpu-load 80
CloudWatch
Dashboard EC2 CPUUtilizationAs the CPU becomes more and more loaded,
the the CPUUtilization metric in CloudWatch also reflects it:
snippet of code to use the output logs in ScriptRunner Adaptavist groovy scripts
/***********/import org.apache.log4j.Loggerimport org.apache.log4j.Level def log = Logger.getLogger("com.scriptname")log.setLevel(Level.DEBUG)/***********/ //and then, for example to print the variable tremlog.debug "trem=${trem}"
|
example :
