Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: introduce --fail-on-ingest-warnings to detect, and treat as errors, warnings from ingest pipeline #1755

Conversation

pkoutsovasilis
Copy link
Contributor

This PR intoduces --fail-on-ingest-warnings that instructs elastic-package to check for warnings on the log of elasticsearch when running the pipeline test.

For example, clone integration repo at this SHA elastic/integrations@389e006

With the code of this PR running the pipeline test inside packages/cisco_asa results in the following:

$ elastic-package test pipeline --fail-on-ingest-warnings
Run pipeline tests for the package
2024/04/09 15:36:29  WARN ingest pipeline warning: character class has '-' without escape
2024/04/09 15:36:29  WARN ingest pipeline warning: nested repeat operator '+' and '?' was replaced with '*' in regular expression /(?:(?<CISCO_DOMAIN_USER:_temp_.cisco.source_username>((?:(LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b))\\)?))?(?:[^,$)]+)?)\$?\)?(?:(, *((?:((?<NUMBER:_temp_.cisco.source_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))):(?:((?<WORD:_temp_.cisco.source_user_security_group_tag_name>\b\w+\b)))|(?:((?<NUMBER:_temp_.cisco.source_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+))))))))))|((?:((?<NUMBER:_temp_.cisco.source_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))):(?:((?<WORD:_temp_.cisco.source_user_security_group_tag_name>\b\w+\b))))))|(?:(?<CISCO_DOMAIN_USER:_temp_.cisco.source_username>((?:(LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b))\\)?))?(?:[^,$)]+)?)\$?\)?)/
2024/04/09 15:36:29  WARN ingest pipeline warning: nested repeat operator '+' and '?' was replaced with '*' in regular expression /(?:(?<CISCO_DOMAIN_USER:_temp_.cisco.destination_username>((?:(LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b))\\)?))?(?:[^,$)]+)?)\$?\)?(?:(, *((?:((?<NUMBER:_temp_.cisco.destination_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))):(?:((?<WORD:_temp_.cisco.destination_user_security_group_tag_name>\b\w+\b)))|(?:((?<NUMBER:_temp_.cisco.destination_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+))))))))))|((?:((?<NUMBER:_temp_.cisco.destination_user_security_group_tag>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))):(?:((?<WORD:_temp_.cisco.destination_user_security_group_tag_name>\b\w+\b))))))|(?:(?<CISCO_DOMAIN_USER:_temp_.cisco.destination_username>((?:(LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b))\\)?))?(?:[^,$)]+)?)\$?\)?)/
2024/04/09 15:36:29  WARN ingest pipeline warning: nested repeat operator '+' and '?' was replaced with '*' in regular expression /Teardown (?:.*?) (?<NOTSPACE:network.transport>\S+) translation from (?<NOTCOLON:_temp_.cisco.source_interface>[^:]*):(?<IPORHOST:source.address>(?:(?:(?:(?:((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:)))(%.+)?)|(?:(?<![0-9])(?:(?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5]))(?![0-9]))))|(?:\b(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62}))*(\.?|\b))))/(?<NUMBER:source.port>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+))))))(\s*\((?<CISCO_USER:_temp_.cisco.source_username>(?:\*\*\*\*\*|(?:(?:LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62}))*(\.?|\b))\\)?(?:(?:[a-zA-Z0-9._-]+))?\$?(?:@(?:\b(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-_]{0,62}))*(\.?|\b)))?(?:, *(?:(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))?(?:(?:(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))):(?:.*?))?)))\))? to (?<NOTCOLON:_temp_.cisco.destination_interface>[^:]*):(?<IP:destination.address>(?:(?:((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:)))(%.+)?)|(?:(?<![0-9])(?:(?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5]))(?![0-9]))))/(?<NUMBER:destination.port>(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))) duration (?<DURATION:_temp_.duration_hms>(?:(?:[+-]?(?:[0-9]+))):(?:(?:[0-5][0-9])):(?:(?:(?:[0-5]?[0-9]|60)(?:[:.,][0-9]+)?)))/
--- Test results for package: cisco_asa - START ---
FAILURE DETAILS:
cisco_asa/log (service elasticsearch logs):



╭───────────┬─────────────┬───────────┬──────────────────────────────┬──────────────────────────────────────────────┬──────────────╮
│ PACKAGE   │ DATA STREAM │ TEST TYPE │ TEST NAME                    │ RESULT                                       │ TIME ELAPSED │
├───────────┼─────────────┼───────────┼──────────────────────────────┼──────────────────────────────────────────────┼──────────────┤
│ cisco_asa │ log         │ pipeline  │ test-additional-messages.log │ PASS                                         │  54.837916ms │
│ cisco_asa │ log         │ pipeline  │ test-anyconnect-messages.log │ PASS                                         │   8.908667ms │
│ cisco_asa │ log         │ pipeline  │ test-asa-fix.log             │ PASS                                         │   9.146291ms │
│ cisco_asa │ log         │ pipeline  │ test-asa-missing-groups.log  │ PASS                                         │   8.268542ms │
│ cisco_asa │ log         │ pipeline  │ test-asa.log                 │ PASS                                         │  112.75425ms │
│ cisco_asa │ log         │ pipeline  │ test-dap-records.log         │ PASS                                         │   4.776375ms │
│ cisco_asa │ log         │ pipeline  │ test-filtered.log            │ PASS                                         │   5.504208ms │
│ cisco_asa │ log         │ pipeline  │ test-hostnames.log           │ PASS                                         │   4.312959ms │
│ cisco_asa │ log         │ pipeline  │ test-non-canonical.log       │ PASS                                         │  11.926584ms │
│ cisco_asa │ log         │ pipeline  │ test-not-ip.log              │ PASS                                         │   6.044875ms │
│ cisco_asa │ log         │ pipeline  │ test-sample.log              │ PASS                                         │  47.160333ms │
│ cisco_asa │ log         │ pipeline  │ test-sgt-tag-name.log        │ PASS                                         │     24.326ms │
│ cisco_asa │ log         │ pipeline  │ test-sip.log                 │ PASS                                         │     5.7505ms │
│ cisco_asa │ log         │ pipeline  │ (service elasticsearch logs) │ FAIL: detected ingest pipeline warnings: 503 │ 1.764223625s │
╰───────────┴─────────────┴───────────┴──────────────────────────────┴──────────────────────────────────────────────┴──────────────╯
--- Test results for package: cisco_asa - END   ---

However, the code at main completes the test without any error. Having such a flag that we can opt in and check for warning is useful to prevent issues, such as this one in the future.

Closes #1754

@taylor-swanson
Copy link
Contributor

It would be nice to surface these warnings all the time, not just when --fail-on-ingest-warnings is given. For new integrations, this would be great, but I could see this being "annoying" for existing ones and could cause lots of spam in CI logs.

The problem here is I didn't even know these logs existed in the first place. What's worse is they are discovered by end users and not devs. Even if we had a way to disable them for elastic-package (like other validations), the warnings will still surface for users.

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from 7faad5f to c067c8f Compare April 10, 2024 08:50
@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from c067c8f to 96e5755 Compare April 10, 2024 09:01
@jsoriano
Copy link
Member

It would be nice to surface these warnings all the time, not just when --fail-on-ingest-warnings is given.

+1, it'd be nice if we can just fail always on these errors, as they are actual issues. We introduced in the past some checks based on errors found in elastic-agent logs (#1256).

@pkoutsovasilis could you try to always enable this check and test with all integrations (adding a comment test integrations) here? If not many of them fail maybe we can go on and always enable this check.

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from 9f3534b to 7c96c1f Compare April 10, 2024 11:42
@jsoriano
Copy link
Member

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@pkoutsovasilis
Copy link
Contributor Author

pkoutsovasilis commented Apr 10, 2024

Overall integrations testing do not look that bad https://buildkite.com/elastic/integrations/builds/10324 although there is an integration that is not detected (cisco_ios). Just pushed a commit that hopefully address this

@pkoutsovasilis
Copy link
Contributor Author

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@pkoutsovasilis
Copy link
Contributor Author

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@pkoutsovasilis
Copy link
Contributor Author

@jsoriano any idea why cisco_ftd in the integration test has a different log format compared to others like this

elasticsearch-1  | {"type": "server", "timestamp": "2024-04-10T12:54:26,235Z", "level": "WARN", "component": "o.e.i.c.GrokProcessor", "cluster.name": "elasticsearch", "node.name": "9e39afe7080b", "message": "character class has '-' without escape", "cluster.uuid": "WbdhEzxGRo6c9Td8pW646g", "node.id": "AATj6t7cTCqOrA8G2NT40Q"  }
elasticsearch-1  | {"type": "server", "timestamp": "2024-04-10T12:54:26,289Z", "level": "WARN", "component": "o.e.i.c.GrokProcessor", "cluster.name": "elasticsearch", "node.name": "9e39afe7080b", "message": "character class has '-' without escape", "cluster.uuid": "WbdhEzxGRo6c9Td8pW646g", "node.id": "AATj6t7cTCqOrA8G2NT40Q"  }
elasticsearch-1  | {"type": "server", "timestamp": "2024-04-10T12:54:26,292Z", "level": "WARN", "component": "o.e.i.c.GrokProcessor", "cluster.name": "elasticsearch", "node.name": "9e39afe7080b", "message": "character class has '-' without escape", "cluster.uuid": "WbdhEzxGRo6c9Td8pW646g", "node.id": "AATj6t7cTCqOrA8G2NT40Q"  }

do we need to support such a format in our log parsing? 🙂

@pkoutsovasilis
Copy link
Contributor Author

test integrations

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from f3fd006 to f9e060c Compare April 10, 2024 16:32
@pkoutsovasilis
Copy link
Contributor Author

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@jsoriano
Copy link
Member

any idea why cisco_ftd in the integration test has a different log format compared to others like this

Not sure if this is the reason, but cisco_ftd supports 7.16, so maybe something changed in 8.x regarding logs.

do we need to support such a format in our log parsing? 🙂

If the reason is the version of Elasticsearch, in principle we need to support since 7.14, the first version where Fleet was GA. So we need to support any log formats used between these versions. Or if possible, other approach could be to configure Elasticsearch to use the same logging format independently of the version.

@pkoutsovasilis
Copy link
Contributor Author

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from ff55ea3 to b771542 Compare April 16, 2024 07:29
@pkoutsovasilis
Copy link
Contributor Author

test integrations

@elasticmachine
Copy link
Collaborator

Created or updated PR in integrations repository to test this version. Check elastic/integrations#9561

@pkoutsovasilis
Copy link
Contributor Author

pkoutsovasilis commented Apr 16, 2024

@jsoriano all integrations having failures related to this feature (pipeline warnings) are fixed and I think this is now good to fly with this check always enabled. integrations run

@jsoriano
Copy link
Member

/test

@jsoriano
Copy link
Member

@pkoutsovasilis there are some tests consistently failing here, could you take a look to them?
It may be a matter of adding a new error to the file of expected errors for cisco_asa. It was expecting 3 errors but it looks like there are 4 now.

@jsoriano
Copy link
Member

Here is the related part of the log about the failure: https://buildkite.com/elastic/elastic-package/builds/2822#018ee670-b8c2-4475-86a2-567e849247e6/126-547

@pkoutsovasilis
Copy link
Contributor Author

Here is the related part of the log about the failure: https://buildkite.com/elastic/elastic-package/builds/2822#018ee670-b8c2-4475-86a2-567e849247e6/126-547

sure thing @jsoriano , thanks for catching that

@pkoutsovasilis
Copy link
Contributor Author

🤦

regular expression has redundant nested repeat operator * /AAA user (?<DATA:_temp_.cisco.aaa_type>.*?) Successful((?:\s*))?: server =((?:\s*)+)?(?<IP:destination.address>(?:(?:((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}))|:)))(%.+)?)|(?:(?<![0-9])(?:(?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5])[.](?:[0-1]?[0-9]{1,2}|2[0-4][0-9]|25[0-5]))(?![0-9])))) [:,] [Uu]ser = (?<CISCO_USER:source.user.name>((LOCAL\\)?((?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b))\\)?(?:[a-zA-Z0-9._-]+)(@(?:\b(?:[0-9A-Za-z][0-9A-Za-z-]{0,62})(?:\.(?:[0-9A-Za-z][0-9A-Za-z-]{0,62}))*(\.?|\b)))?(, *(?:(?:(?:(?<![0-9.+-])(?>[+-]?(?:(?:[0-9]+(?:\.[0-9]+)?)|(?:\.[0-9]+)))))))?))/

@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch 2 times, most recently from 95a7819 to 0b51e62 Compare April 16, 2024 11:55
@pkoutsovasilis pkoutsovasilis force-pushed the pkoutsovasilis/support_pipeline_warnings branch from 0b51e62 to b3da911 Compare April 16, 2024 12:16
internal/testrunner/runners/pipeline/runner.go Outdated Show resolved Hide resolved
cmd/testrunner.go Outdated Show resolved Hide resolved
@pkoutsovasilis
Copy link
Contributor Author

/test

Copy link
Member

@jsoriano jsoriano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

@pkoutsovasilis pkoutsovasilis merged commit f439b96 into elastic:main Apr 16, 2024
3 checks passed
@pkoutsovasilis pkoutsovasilis deleted the pkoutsovasilis/support_pipeline_warnings branch April 16, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] check for warnings from elastic-search during test pipelines
4 participants