feat(elk-monitoring): Add Kibana configuration for Pagopa Payopt logging [PAGOPA-2178] #2445
+320
−0
Conversation
This file contains 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
jacopocarlini
changed the title
jacopocarlini
changed the title
jacopocarlini
changed the title
… index management refactor(elk-monitoring): update index references to use log_index_pattern for consistency fix(data-view.json): change title to use dynamic index pattern instead of static value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit introduces a new Terraform configuration file for setting up Kibana monitoring for Pagopa Payopt logs. It includes the creation of a Kibana space, ingest pipeline, ILM policy, component template, index template, and data view. These resources are essential for managing and visualizing log data effectively in Kibana.
List of changes
Motivation and context
Jira Task
Type of changes
Does this introduce a change to production resources with possible user impact?
Does this introduce an unwanted change on infrastructure? Check terraform plan execution result
Other information
If PR is partially applied, why? (reserved to mantainers)