x-codeguru_profiler ¶

          x-codeguru_profiler:
    Profiler01:
      Properties: {} # No properties need to be set. ECS Compose-X will do all that.

         

Properties ¶

Ths properties allow to use the same definition as in AWS Syntax Reference.

MacroParameters ¶

AppendStackId ¶

Type: Boolean Description: Allows you to automatically add the stack ID to the provided Profiling Group Name so you can have multiple profiling groups of the same logical name in your compose definition but different names when deploying to the same account and same AWS region.

Tip

We recommend to set the value to True at all times, but did not make it default.

Lookup ¶

See Lookup for syntax.

Note

For Lookup as when you create it, the profiling group name is available via AWS_CODEGURU_PROFILER_GROUP_NAME environment variable.

Example ¶

           x-codeguru_profiler:
    Profiler01:
      Properties: {}
    Services:
      service01
        Access: RW
        ReturnValues:
          ProfileName: AWS_CODEGURU_PROFILER_GROUP_NAME

          

Attention

The only valid access mode is RW You cannot use ReturnValues for this module.

Code Example ¶

Full Applications code used for this sort of testing can be found here

JSON Schema ¶

Model ¶

services.x-codeguru_profiler specification ¶

services.x-codeguru_profiler
The services.x-codeguru_profiler specification for ComposeX
oneOf	type	string
	type	boolean
	type	object

Definition ¶

            {
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "services.x-logging.spec.json",
  "id": "services.x-codeguru_profiler",
  "title": "services.x-codeguru_profiler specification",
  "description": "The services.x-codeguru_profiler specification for ComposeX",
  "oneOf": [
    {
      "type": "string"
    },
    {
      "type": "boolean"
    },
    {
      "type": "object"
    }
  ]
}

           

Test files ¶

You can find the test files here to use as reference for your use-case.