69
15
6
Events
Compatibility with php 8.1
Recent documentations says that version 2 is for php 7.4 and 8.1. However: the composer.json for 2.2.x requires only php 7.4.
Can you change this?
Compatibility with php 8.1
@ekomurz Feel free to open the issue again if it doesn't work.
Compatibility with php 8.1
@ekomurz Fixed in v2.2.2. Thanks!
fix: composer.json should allow php7 and php8 for 2.x version
helm: bump agent chart version from 0.6.0 to 0.7.0
From the changelog
- Helm chart: Add support for templates inside of configMap.content (@ts-mini)
- Add the necessary rbac to support eventhandler integration (@nvanheuverzwijn)
PR Description
Bump the chart version from 0.6.0 to 0.7.0 to incorporate recent changes
fix: add rbac for eventhandler (#3076)
[Agent Management] Check remote cache for validity using url hash (#2936)
doc: make version section more readable
Release v3.1.0 on packagist.org
Dear @nvanheuverzwijn,
Thanks for merging my PR #8. I'd like to use the newly released version 3.1.0 in my PHP project. To be able to install the new version using composer, the new version must be available on Packagist.org. I see that the changes are not automatically synced and requires a manual push from your side.
Would you please be so kind to push the new version to Packagist? Thanks in advance!
Best,
John
Release v3.1.0 on packagist.org
@Jhnbrn90 Alright, it's done! Let me know if there's any other issues!
Thank you!
Release v3.1.0 on packagist.org
Hey @Jhnbrn90 ,
I will definitely take a look!
Thanks
fix: add rbac for eventhandler
fix(helm): add rbac for eventhandler
@rfratto done! Thank you!
fix: add rbac for eventhandler
fix(helm): add rbac for eventhandler
PR Description
Add rbac value in order for eventhandler to read kubernets events. According to https://grafana.com/docs/agent/latest/configuration/integrations/integrations-next/eventhandler-config/, grafana-agent need to be able to read the events resources.
Use expected \Monolog\LogRecord object in handler
In version 3.x, Monolog has updated from using a simple array to represent the log record, to using a dedicated LogRecord object to represent the log record in the AbstractProcessingHandler, which the LogDNAHandler class extends.
In this commit, the LogdnaHandler has been updated to accept the \Monolog\LogRecord object as parameter over the $record array.
Merge pull request #8 from Jhnbrn90/compat-monolog-3
Use expected \Monolog\LogRecord object in handler
Use expected \Monolog\LogRecord object in handler
In version 3.x, Monolog has updated from using a simple array to represent the log record, to using a dedicated LogRecord object to represent the log record in the AbstractProcessingHandler, which the LogdnaHandler class extends.
In this PR, the LogdnaHandler has been updated to accept the \Monolog\LogRecord object as parameter over the $record array.
Source: https://github.com/Seldaek/monolog/blob/main/UPGRADE.md
Log records have been converted from an array to a Monolog\LogRecord object with public (and mostly readonly) properties. e.g. instead of doing $record['context'] use $record->context. In formatters or handlers if you rather need an array to work with you can use $record->toArray() to get back a Monolog 1/2 style record array. This will contain the enum values instead of enum cases in the level and level_name keys to be more backwards compatible and use simpler data types.
@nvanheuverzwijn
