[APM] Updated eem schema #188763
[APM] Updated eem schema #188763
Conversation
botelastic
bot
added
ci:project-deploy-observability
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
| @@ -72,7 +72,10 @@ export async function getEntities({ | |||
|
|
|||
| return entities.map((entity): ServiceEntities => { | |||
| return { | |||
| serviceName: entity.entity.identityFields.service.name, | |||
| serviceName: entity.service.name, | |||
| environment: Array.isArray(entity.service?.environment) // TODO fix this in the EEM | |||
There was a problem hiding this comment.
Q: Do we need to support multiple environments? And how do we want to fix it - have a single environment or have an array (I see currently we get the first one in case of an array)?
There was a problem hiding this comment.
We support services with multiple environments already. In service inventory we group them. This seems to be introduces by the recent changes in EEM. Which needs to be fixed in their schema.
If the environment exists they return a string. If the environment is empty they return an empty array. This needs to be consistent. I need to create an issue
💚 Build Succeeded
Metrics [docs]Async chunks
History |
kpatticha
added
the
release_note:skip
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
Summary
closes: #188761
changes
logRatePerMinutetologRate(EEM change)