[azure_functions] Parse stringified 'properties' field in Azure Functions app logs#15595
Merged
devamanv merged 9 commits intoelastic:mainfrom Oct 8, 2025
Merged
Conversation
🚀 Benchmarks reportTo see the full report comment with |
muthu-mps
reviewed
Oct 8, 2025
packages/azure_functions/data_stream/functionapplogs/fields/fields.yml
Outdated
Show resolved
Hide resolved
packages/azure_functions/data_stream/functionapplogs/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
zmoog
reviewed
Oct 8, 2025
packages/azure_functions/data_stream/functionapplogs/fields/fields.yml
Outdated
Show resolved
Hide resolved
packages/azure_functions/data_stream/functionapplogs/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
zmoog
approved these changes
Oct 8, 2025
muthu-mps
reviewed
Oct 8, 2025
| { | ||
| "azure": { | ||
| "category": "FunctionAppLogs", | ||
| "event_primary_stamp_name": "waws-prod-blu-125", |
Contributor
There was a problem hiding this comment.
Should the event_stamp fields be under azure.function.* or azure.* If these are generic fields then we can have at top level.
Contributor
Author
There was a problem hiding this comment.
These fields are event-specific, and not to a function execution per se. That's why they have been kept at the top level.
💚 Build Succeeded
History
cc @devamanv |
muthu-mps
approved these changes
Oct 8, 2025
|
Package azure_functions - 0.11.0 containing this change is available at https://epr.elastic.co/package/azure_functions/0.11.0/ |
agithomas
pushed a commit
to agithomas/integrations
that referenced
this pull request
Oct 30, 2025
tehbooom
pushed a commit
to tehbooom/integrations
that referenced
this pull request
Nov 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
This change updates the Azure Functions ingest pipeline to correctly parse the properties field, which is often received as a stringified JSON. Previously, nested fields inside properties were not parsed and accessible in Elasticsearch.
The pipeline now:
propertiesfield is a string.level,appName,message) available for mapping and querying.This ensures that all fields inside properties are properly indexed and usable in dashboards, alerts, and queries.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
elastic-packageto the running Kibana instanceelastic-package install --zip azure_functions-0.11.0.zipFunction Premiumwas observed to exhibit such behaviorDiscoversection, and in thelogs-*data view, add the filterdata_stream.dataset: azure_functions.functionapplogs. The documents should have the fields underfunctionfield, and no pipeline errors.Related issues
Screenshots