amazonka-appmesh-2.0: Amazon App Mesh SDK.
Copyright(c) 2013-2023 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellSafe-Inferred
LanguageHaskell2010

Amazonka.AppMesh.Types.FileAccessLog

Description

 
Synopsis

Documentation

data FileAccessLog Source #

An object that represents an access log file.

See: newFileAccessLog smart constructor.

Constructors

FileAccessLog' 

Fields

  • format :: Maybe LoggingFormat

    The specified format for the logs. The format is either json_format or text_format.

  • path :: Text

    The file path to write access logs to. You can use /dev/stdout to send access logs to standard out and configure your Envoy container to use a log driver, such as awslogs, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.

     <note> <p>The Envoy process must have write permissions to the path that you specify here. Otherwise, Envoy fails to bootstrap properly.</p> </note>

Instances

Instances details
FromJSON FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

ToJSON FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

Generic FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

Associated Types

type Rep FileAccessLog :: Type -> Type #

Read FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

Show FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

NFData FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

Methods

rnf :: FileAccessLog -> () #

Eq FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

Hashable FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

type Rep FileAccessLog Source # 
Instance details

Defined in Amazonka.AppMesh.Types.FileAccessLog

type Rep FileAccessLog = D1 ('MetaData "FileAccessLog" "Amazonka.AppMesh.Types.FileAccessLog" "amazonka-appmesh-2.0-GBIHUgXnP8s1LEJyvNe1ca" 'False) (C1 ('MetaCons "FileAccessLog'" 'PrefixI 'True) (S1 ('MetaSel ('Just "format") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe LoggingFormat)) :*: S1 ('MetaSel ('Just "path") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 Text)))

newFileAccessLog Source #

Create a value of FileAccessLog with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:format:FileAccessLog', fileAccessLog_format - The specified format for the logs. The format is either json_format or text_format.

$sel:path:FileAccessLog', fileAccessLog_path - The file path to write access logs to. You can use /dev/stdout to send access logs to standard out and configure your Envoy container to use a log driver, such as awslogs, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.

 <note> <p>The Envoy process must have write permissions to the path that you specify here. Otherwise, Envoy fails to bootstrap properly.</p> </note>

fileAccessLog_format :: Lens' FileAccessLog (Maybe LoggingFormat) Source #

The specified format for the logs. The format is either json_format or text_format.

fileAccessLog_path :: Lens' FileAccessLog Text Source #

The file path to write access logs to. You can use /dev/stdout to send access logs to standard out and configure your Envoy container to use a log driver, such as awslogs, to export the access logs to a log storage service such as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file system to write the files to disk.

 <note> <p>The Envoy process must have write permissions to the path that you specify here. Otherwise, Envoy fails to bootstrap properly.</p> </note>