« blib/lib/Paws/ManagedBlockchain/NodeFabricAttributes.pm
↑ Summary
blib/lib/Paws/ManagedBlockchain/NodeFrameworkAttributes.pm »
| 1 | # Generated by default/object.tt | ||
| 2 | package Paws::ManagedBlockchain::NodeFabricLogPublishingConfiguration; | ||
| 3 | use Moose; | ||
| 4 | has ChaincodeLogs => (is => 'ro', isa => 'Paws::ManagedBlockchain::LogConfigurations'); | ||
| 5 | has PeerLogs => (is => 'ro', isa => 'Paws::ManagedBlockchain::LogConfigurations'); | ||
| 6 | |||
| 7 | 1; | ||
| 8 | |||
| 9 | ### main pod documentation begin ### | ||
| 10 | |||
| 11 | =head1 NAME | ||
| 12 | |||
| 13 | Paws::ManagedBlockchain::NodeFabricLogPublishingConfiguration | ||
| 14 | |||
| 15 | =head1 USAGE | ||
| 16 | |||
| 17 | This class represents one of two things: | ||
| 18 | |||
| 19 | =head3 Arguments in a call to a service | ||
| 20 | |||
| 21 | Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. | ||
| 22 | Each attribute should be used as a named argument in the calls that expect this type of object. | ||
| 23 | |||
| 24 | As an example, if Att1 is expected to be a Paws::ManagedBlockchain::NodeFabricLogPublishingConfiguration object: | ||
| 25 | |||
| 26 | $service_obj->Method(Att1 => { ChaincodeLogs => $value, ..., PeerLogs => $value }); | ||
| 27 | |||
| 28 | =head3 Results returned from an API call | ||
| 29 | |||
| 30 | Use accessors for each attribute. If Att1 is expected to be an Paws::ManagedBlockchain::NodeFabricLogPublishingConfiguration object: | ||
| 31 | |||
| 32 | $result = $service_obj->Method(...); | ||
| 33 | $result->Att1->ChaincodeLogs | ||
| 34 | |||
| 35 | =head1 DESCRIPTION | ||
| 36 | |||
| 37 | Configuration properties for logging events associated with a peer node | ||
| 38 | owned by a member in a Managed Blockchain network. | ||
| 39 | |||
| 40 | =head1 ATTRIBUTES | ||
| 41 | |||
| 42 | |||
| 43 | =head2 ChaincodeLogs => L<Paws::ManagedBlockchain::LogConfigurations> | ||
| 44 | |||
| 45 | Configuration properties for logging events associated with chaincode | ||
| 46 | execution on a peer node. Chaincode logs contain the results of | ||
| 47 | instantiating, invoking, and querying the chaincode. A peer can run | ||
| 48 | multiple instances of chaincode. When enabled, a log stream is created | ||
| 49 | for all chaincodes, with an individual log stream for each chaincode. | ||
| 50 | |||
| 51 | |||
| 52 | =head2 PeerLogs => L<Paws::ManagedBlockchain::LogConfigurations> | ||
| 53 | |||
| 54 | Configuration properties for a peer node log. Peer node logs contain | ||
| 55 | messages generated when your client submits transaction proposals to | ||
| 56 | peer nodes, requests to join channels, enrolls an admin peer, and lists | ||
| 57 | the chaincode instances on a peer node. | ||
| 58 | |||
| 59 | |||
| 60 | |||
| 61 | =head1 SEE ALSO | ||
| 62 | |||
| 63 | This class forms part of L<Paws>, describing an object used in L<Paws::ManagedBlockchain> | ||
| 64 | |||
| 65 | =head1 BUGS and CONTRIBUTIONS | ||
| 66 | |||
| 67 | The source code is located here: L<https://github.com/pplu/aws-sdk-perl> | ||
| 68 | |||
| 69 | Please report bugs to: L<https://github.com/pplu/aws-sdk-perl/issues> | ||
| 70 | |||
| 71 | =cut | ||
| 72 |