New ONAP Component Checklist

Add this procedure to the Project Proposal Template

By following a few simple rules:

• Your component's output will be indexed automatically. 
• Analytics will be able to trace invocation through your component.

Obligations fall into two categories:

1. Conventions regarding configuration, line format and output. 
2. Ensuring the propagation of contextual information. 

You must:

1. Choose a Logging provider and/or EELF. Decisions, decisions.
2. Create a configuration file based on an existing archetype. See 48534506.
3. Read your configuration file when your components initialize logging.
4. Write logs to a standard location so that they can be shipped by Filebeat for indexing. See 48534506.
5. Report transaction state:
   1. Retrieve, default and propagate RequestID. See 48534506.
   2. At each invocation of one ONAP component by another:
      1. Initialize and propagate InvocationID. See 48534506.
      2. Report INVOKE and SYNCHRONOUS markers in caller. 
      3. Report ENTRY and EXIT markers in recipient. 
6. Write useful logs!

 They are unordered.