20 time tracker with log analytics azure (#23)

* Add Azure Log Analytics Workspace to time_token_tracker.py

* Encryption added and other improvements

* Add Issue Templates. Update Docs and Reademe

* Update links

Author: owndev

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,80 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Contacting individual members, contributors, or leaders privately, outside designated community mechanisms, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at opensource@github.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at <https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at <https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.

.github/CONTRIBUTING.md

@@ -0,0 +1,73 @@
+# Welcome to Open-WebUI-Functions contributing guide <!-- omit in toc -->
+
+Thank you for investing your time in contributing to our project!
+
+Read our [Code of Conduct](https://own.dev/github-owndev-open-webui-functions-code-of-conduct) to keep our community approachable and respectable.
+
+In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR.
+
+Use the table of contents icon <img alt="Table of contents icon" src="../docs/images/table-of-contents.png" width="25" height="25" /> on the top left corner of this document to get to a specific section of this guide quickly.
+
+## New contributor guide
+
+To get an overview of the project, read the [README](https://own.dev/github-owndev-open-webui-functions) file. Here are some resources to help you get started with open source contributions:
+
+- [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)
+- [Set up Git](https://docs.github.com/en/get-started/git-basics/set-up-git)
+- [GitHub flow](https://docs.github.com/en/get-started/using-github/github-flow)
+- [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests)
+
+
+## Getting started
+
+For more information on how we write our markdown files, see "[Using Markdown in GitHub](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)."
+
+### Issues
+
+#### Create a new issue
+
+If you spot a problem, [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://own.dev/github-owndev-open-webui-functions-issues-new).
+
+#### Solve an issue
+
+Scan through our [existing issues](https://own.dev/github-owndev-open-webui-functions-issues) to find one that interests you. You can narrow down the search using `labels` as filters. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix.
+
+### Make Changes
+
+#### Make changes in the UI
+
+Click **Make a contribution** at the bottom of any docs page to make small changes such as a typo, sentence fix, or a broken link. This takes you to the `.md` file where you can make your changes and [create a pull request](#pull-request) for a review.
+
+ <img src="../docs/images/contribution_cta.png" />
+
+#### Make changes locally
+
+1. Fork the repository.
+- Using GitHub Desktop:
+  - [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop.
+  - Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)!
+
+- Using the command line:
+  - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them.
+
+3. Create a working branch and start with your changes!
+
+### Commit your update
+
+Commit the changes once you are happy with them.
+
+### Pull Request
+
+When you're finished with the changes, create a pull request, also known as a PR.
+- Fill the "Ready for review" template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request.
+- Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one.
+- Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge.
+Once you submit your PR, a team member will review your proposal. We may ask questions or request additional information.
+- We may ask for changes to be made before a PR can be merged. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
+- If you run into any merge issues, checkout this [git tutorial](https://github.com/skills/resolve-merge-conflicts) to help you resolve merge conflicts and other issues.
+
+### Your PR is merged!
+
+Congratulations :tada::tada: the **Open-WebUI-Functions** team thanks you :sparkles:.
+
+Once your PR is merged, your posts will be made public.

.github/ISSUE_TEMPLATE/contribute-your-own-feature.yaml

@@ -0,0 +1,78 @@
+name: Contribute your own feature
+description: Propose and contribute a self-implemented feature for this project.
+labels:
+  - enhancement
+  - contribution
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thank you for contributing to this project!**  
+        This template is intended for contributors who plan to **submit their own implementation** of a new feature or improvement.
+
+        Please fill out all relevant sections to help the maintainers review and integrate your work efficiently.
+
+        - Make sure you’ve read the [Contributing Guide](https://own.dev/github-owndev-open-webui-functions-contributing).
+        - Before proceeding, open this issue to **coordinate with maintainers** and avoid duplicate work.
+
+  - type: checkboxes
+    id: agreement
+    attributes:
+      label: Contribution Terms
+      description: Confirm that you've reviewed the necessary guidelines and intend to contribute code.
+      options:
+        - label: I have reviewed the project’s [Code of Conduct](https://own.dev/github-owndev-open-webui-functions-code-of-conduct) and contribution guidelines.
+          required: true
+        - label: I plan to implement this feature myself and submit a pull request.
+          required: true
+
+  - type: input
+    attributes:
+      label: Feature title
+      description: A short, clear name for the feature you're implementing.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Feature overview
+      description: |
+        Briefly describe the feature you're planning to implement:
+        - What problem does it solve or what benefit does it bring?
+        - Who are the target users or use cases?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Implementation details
+      description: |
+        Describe your planned approach or architecture for implementing this feature.
+        Include:
+        - Which components/modules will be affected
+        - APIs, libraries, or technologies you intend to use
+        - Any design decisions or constraints
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Tasks and milestones
+      description: Break down the work into actionable steps or milestones. This will help with tracking progress.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Questions or areas for feedback
+      description: |
+        Do you have any uncertainties, decisions to validate, or places where you'd like early feedback from maintainers?
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional context or references
+      description: Link related discussions, documents, code snippets, or external resources.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/documentation-update.yaml

@@ -0,0 +1,25 @@
+name: Documentation update
+description: Suggest improvements or changes to the documentation.
+labels:
+  - documentation
+body:
+  - type: input
+    attributes:
+      label: Documentation area
+      description: What part of the documentation needs improvement? (e.g., README, API docs, Setup guide)
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Suggested improvement
+      description: Describe what should be changed or clarified and why.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add references, links, or examples to help understand your suggestion.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/question-or-support.yaml

@@ -0,0 +1,32 @@
+name: Question or Support
+description: Ask a question or request help using the project.
+labels:
+  - question
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Need help or have a question?**  
+        This form is for general usage questions or support requests.  
+        Please check the [documentation](https://own.dev/github-owndev-open-webui-functions) and existing [issues](https://own.dev/github-owndev-open-webui-functions-issues) before submitting.
+
+  - type: input
+    attributes:
+      label: Question summary
+      description: Briefly describe your question or what you need help with.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Details
+      description: Please describe the question or issue in more detail. Include context, logs, error messages, etc. if applicable.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: What have you tried?
+      description: Share what you've already tried to solve the issue on your own.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/report-a-bug.yaml

@@ -0,0 +1,53 @@
+name: Report a bug
+description: Report an issue that you encountered while using the project.
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thanks for reporting a bug!**  
+        Please complete the information below to help us reproduce and fix the issue.
+
+  - type: input
+    attributes:
+      label: Bug title
+      description: A brief summary of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: |
+        What went wrong? Include:
+        - What you expected to happen
+        - What actually happened
+        - Any error messages or screenshots
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Describe the steps we need to take to see the issue. Be as specific as possible.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Environment
+      description: |
+        Provide relevant environment details:
+        - OS, browser/device (if relevant)
+        - Software version or commit hash
+        - Any configuration or plugins used
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add links to logs, screenshots, or related issues if available.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/submit-an-idea-or-proposal.yml

@@ -0,0 +1,45 @@
+name: Submit an idea or proposal
+description: Suggest a general idea or concept for discussion, not necessarily planned for immediate implementation.
+labels:
+  - idea
+  - discussion
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Have an idea to share?**  
+        Use this form to submit general proposals, conceptual ideas, or directions for future development. This is a space for open-ended discussions that might not yet be tied to a concrete implementation.
+
+        > If you're planning to contribute code for your idea, please use the **"Contribute your own feature"** template instead.
+
+  - type: input
+    attributes:
+      label: Idea title
+      description: A clear and concise title for your idea or proposal.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe your idea
+      description: |
+        Describe your idea or proposal in detail. Consider including:
+        - What problem or opportunity you're addressing
+        - How this could improve the project
+        - Any inspiration or background
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Possible directions or next steps
+      description: What could be explored next? Are there any potential ways this idea could be evaluated or tested?
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any links, discussions, screenshots, or references to support your idea.
+    validations:
+      required: false