Enhancement Request: Customizable Context Tags for Monitoring Entries.

[andre-hoffmann]

Feature Request: Tag Context in Laravel Pulse Monitoring Entries

Overview:
Applications leveraging Laravel Pulse for monitoring, especially in multi-tenant environments, greatly benefit from the ability to add specific context tags to each monitoring entry. This feature is currently missing, limiting the depth of insights that can be derived from the monitoring data.

Request:
I propose the introduction of customizable context tags for each monitoring entry within Laravel Pulse. This would allow developers to annotate entries with tags for tenant ID, feature usage, and more, similar to functionalities offered by tools like laravel/telescope. Such tagging would enhance data filtering, analysis, and the overall utility of the monitoring tool.

Benefits:

• Enhanced data analysis and filtering based on customizable tags.
• Improved troubleshooting and operational management through detailed context.
• Greater flexibility in monitoring across diverse and complex application scenarios.

Question:
Is there an interest in incorporating tagging functionality into Laravel Pulse? I believe this feature would significantly elevate its monitoring capabilities by providing more actionable insights.

Additionally, I am willing to contribute to this enhancement by creating a pull request. Could you guide me on the preferred approach or any specific contribution guidelines to follow for this feature?

[timacdonald]

Hi, @andre-hoffmann, we aren't currently considering adding tags to Pulse.

You are welcome to open a PR with the feature, but we wouldn't know if we would accept the feature until we saw the implementation to weigh up the complexity / benefit.

Laravel's contribution guidelines can be see at https://laravel.com/docs/11.x/contributions.