initial implementation of otel metrics

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@krakend.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing
+
+Thank you for your interest in contributing to KrakenD-OTEL, there are several ways
+you can contribute and make this project more awesome, please see below:
+
+## Reporting an Issue
+
+If you believe you have found an issue with the code please do not hesitate to file an issue in [Github](https://github.com/krakend/krakend-otel/issues). When
+filing the issue please describe the problem with the maximum level of detail
+and the steps to reproduce the problem, including information about your
+environment.
+
+You can also open an issue requesting for help or doing a question and it's
+also a good way of contributing since other users might be in a similar
+position.
+
+Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Code Contributions
+
+When contributing to this repository, it is generally a good idea to discuss
+the change with the owners before investing a lot of time coding. The process
+could be:
+
+1. Open an issue explaining the improvment or fix you want to add
+2. [Fork the project](https://github.com/krakend/krakend-otel/fork)
+3. Code it in your fork
+4. Submit a [pull request](https://help.github.com/articles/creating-a-pull-request) referencing the issue
+
+
+Your work will then be reviewed as soon as possible (suggestions about some
+changes, improvements or alternatives may be given).
+
+**Don't forget to add tests**, make sure that they all pass!
+
+# Help with Git
+
+Once the repository is forked, you should track the upstream (original) one
+using the following command:
+
+    git remote add upstream https://github.com/krakend/krakend-otel.git
+
+Then you should create your own branch:
+
+    git checkout -b <prefix>/<micro-title>-<issue-number>
+
+Once your changes are done (`git commit -am '<descriptive-message>'`), get the
+upstream changes:
+
+    git checkout master
+    git pull --rebase origin master
+    git pull --rebase upstream master
+    git checkout <your-branch>
+    git rebase master
+
+Finally, publish your changes:
+
+    git push -f origin <your-branch>
+
+You should be now ready to make a pull request.

Makefile

@@ -0,0 +1,9 @@
+test:
+	go test ./client/...
+	go test ./config/...
+	go test ./exporter/...
+	go test ./io/...
+	go test ./lura/...
+	go test ./state/...
+	go test ./router/...
+.PHONY: test