all: remove confusing fail- prefix from error messages - #7105
Conversation
🌐 Coverage report
|
This was originally added to a pipeline with a specific context of adding a machine-friendly tag to error.message, but through miscommunication was included in all subsequent extended error.message implementations.
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
|
Package bitwarden - 1.0.1 containing this change is available at https://epr.elastic.co/search?package=bitwarden |
|
Package cisco_nexus - 0.14.2 containing this change is available at https://epr.elastic.co/search?package=cisco_nexus |
|
Package crowdstrike - 1.16.1 containing this change is available at https://epr.elastic.co/search?package=crowdstrike |
|
Package juniper_srx - 1.13.1 containing this change is available at https://epr.elastic.co/search?package=juniper_srx |
|
Package rapid7_insightvm - 1.0.1 containing this change is available at https://epr.elastic.co/search?package=rapid7_insightvm |
|
Package ti_misp - 1.18.2 containing this change is available at https://epr.elastic.co/search?package=ti_misp |
|
Package trellix_epo_cloud - 1.0.2 containing this change is available at https://epr.elastic.co/search?package=trellix_epo_cloud |
|
Package vectra_detect - 1.0.1 containing this change is available at https://epr.elastic.co/search?package=vectra_detect |
This was originally added to a pipeline with a specific context of adding a machine-friendly tag to error.message, but through miscommunication was included in all subsequent extended error.message implementations.
What does this PR do?
Removes a confusing prefix from enhanced
error.messagefields.This was originally added to a pipeline with a specific context of adding a machine-friendly tag to
error.message, but through miscommunication was included in all subsequent extendederror.messageimplementations.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots