c8y3

# Requests * to get all streams ``` GET /streams ``` * to get a given stream ``` GET /streams/65bc9effed531b17498c5425 => { "id": "65bc9effed531b17498c5425", "creator_user_id": "admin", "outputs": [], "matching_type": "AND",...

It would be interesting to export the rule alone. And try to reproduce the problem starting from an empty graylog.

# Introduction This is a (hopefully) complete description of the encoding we want to have for the various kind of alert rules # Encoding of the conditions The conditions are...

Fixed for rules, but same problem with list cloning.

A test for this: ``` def test_update_alert_rule_title_should_not_fail(self): title = 'aaa' rule = self._graylog.create_alert_rule_count(title, _PERIOD) response = self._graylog.update_alert_rule(title, {**rule, 'title': 'new_title'}) self.assertEqual('new_title', response['title']) ```

The root issue is that alert rules are identified by their titles when unique identifiers should be used instead

I put some troubleshooting information here https://github.com/airbus-cyber/graylog-plugin-logging-alert/wiki/Troubleshooting-and-workarounds. However, I am unsure how to fix this problem. Hence the "Medium" size. In any case, the issue seems related with https://issues.sonatype.org/browse/OSSRH-51097. The...

Some steps to check in order to initiate the correction : * check we can log in https://s01.oss.sonatype.org/#welcome (the new server) * check we can log in JIRA https://issues.sonatype.org/browse/OSSRH-76364 in...

Implementation as it is now, works: "group by" fields are sufficient and event fields are not used. Remove split fields. We must be careful during import, if there are split...

Remark: think about updating the script to verify the rules before they are imported.