This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
instana ELK plugin is not working as expected if we use someother logshipper like vector
out setup Instana version : 241 Elastic version 8.2 Kibana : Stack Management 8.2.3 vector: 0.27.0-debian if I click on pod or container link as it launching the correct kibana dashboard without any logs as there are some issue in filter string it...
Provide level WARN for Docker version of Instana agent
In https://www.ibm.com/docs/en/instana-observability/current?topic=requirements-installing-host-agent-docker#installation INSTANA_LOG_LEVEL does not provide the level WARN. I guess this is an issue and should be added. Esp. for consistency.
Hello, Here is some infos about the request. We highly use custom headers to get contextual informations about HTTP calls . For instance device type, application version etc ..Currently we can filter these informations on the view Application> ...
Hello, Today the feature 'Logs' provide only warning and error log levels.We would find it valuable to also have a log level info because it provides a lot of contextual infos. One thing to point out is that if log levels info would be tracked in ...
It’s nice to see we can navigate to Splunk directly from Instana however I still see some enhancements can be made like below, Support of custom names for field names for PODs E.g: As per Instana the POD name key will be kubernetes.pod_name howeve...
Parse json formatted logs to generate fields and extract log level
We're writing lot's of logs in json format as this is very helpful with other log management solutions (Graylog2, Datadog) to parse these logs into fields and have very searchable data. This would be necessary for us to further use Instana Log ana...
Support for jboss logging version 3.4.1 without programmatic API
For making the JBoss deployment lighter, and for reducing downtime while deployments, we consider that using jboss logging is more convenient than log4j. Unfortunately, this logging framework is not supported by instana (see case #30712). So then,...
We're currently writing java logs with logback/slf4j. Using the logstash ArgumentsJsonProvider in our logback.xml this allows us to extend the log message with context information like stack_traces, logger_name, log level but also custom informati...
Do not place IBM confidential, company confidential, or personal information into any field.