Demonstrate how to set the Resource for LogEmitterProvider

[tigrannajaryan]

Description

Added a Resource to the logs example to make it more complete.
Previously it was using the built-in Resource. Now it adds the
service.name and service.instance.id attributes.

The resulting emitted log records look like this:

Resource labels:
     -> telemetry.sdk.language: STRING(python)
     -> telemetry.sdk.name: STRING(opentelemetry)
     -> telemetry.sdk.version: STRING(1.5.0)
     -> service.name: STRING(shoppingcart)
     -> service.instance.id: STRING(instance-12)
InstrumentationLibraryLogs #0
InstrumentationLibrary __main__ 0.1
LogRecord #0
Timestamp: 2021-10-14 18:33:43.425820928 +0000 UTC
Severity: ERROR
ShortName:
Body: Hyderabad, we have a major problem.
Trace ID: ce1577e4a703f42d569e72593ad71888
Span ID: f8908ac4258ceff6
Flags: 1

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Run the example and watch the Collector's logging exporter output.

Does This PR Require a Contrib Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated Not needed
• Unit tests have been added Not applicable. Example.
• Documentation has been updated

[tigrannajaryan]

@open-telemetry/python-approvers while trying to fix the lint error I accidentally pushed the commit in this PR to the logs branch directly. Can someone please revert so that this undergoes a proper review first? Apologies for the trouble.

[tigrannajaryan]

Let me know if you prefer me to submit a PR that reverts this one first and then create a new PR to review this change properly.

[codeboten]

🤔 i'm surprised branch protection didn't prevent that. @lzchen @ocelotl @owais

[NathanielRN]

Yeah we probably need to edit the **/** rule to make branches that match this to be "protected" @ocelotl

[lzchen]

@tigrannajaryan
Did you force push directly to the log branch in origin?

[tigrannajaryan]

Did you force push directly to the log branch in origin?

Yes, instead of pushing to my fork I accidentally pushed to the origin.

[lzchen]

@tigrannajaryan
Weird, even I'm not able to force push as a python maintainer, maybe you have some super power xD.

That being said, I'm disabling it temporarily to revert the change you pushed. Feel free to send another PR for the original issue.

[tigrannajaryan]

@lzchen sorry for mess and thanks for fixing. I created a new PR: #2209