matomo-org / matomo-org/plugin-LogViewer
Log environment info in core and let users search for all log messages from this environment
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 13
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 8
Description
This is more of a change to core, but we should probably log the current DI environment as well (ie, tracker, cli, web (doesn't exist yet)). This way, we could exclude tracker logs from the LogViewer easily (even if the tag is for a plugin because the log was in the plugin's dimension or something). I will probably create a 3.0 issue for this.
https://github.com/piwik/piwik/issues/7239#issuecomment-139045034
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Matomo issue discussion, then locate the core logging entry points and the LogViewer search/filter code. The issue proposes recording the DI environment, such as tracker or CLI, and allowing searches to exclude an environment; the exact scope, files, and acceptance criteria still need to be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100