All Topics

Top

All Topics

We are in the process of virtualizing our environments and then we are facing the question of whether to use multiple cluster masters or to have fewer cluster masters that serve more indexers each. H... See more...
We are in the process of virtualizing our environments and then we are facing the question of whether to use multiple cluster masters or to have fewer cluster masters that serve more indexers each. However, we don’t know how to go about it. Therefore the question, what are the scalability rules for a cluster master?
Hello Splunkers, is there anyone on the community that would be willing to talk with me about Splunk use cases for measuring, analyzing and communicating large amounts of data for carbon impact simi... See more...
Hello Splunkers, is there anyone on the community that would be willing to talk with me about Splunk use cases for measuring, analyzing and communicating large amounts of data for carbon impact similar to the SAP/NHL Venue Metrics Platform? Mick11
Hi,   Rather new to splunk. I got some logs ingested but they are showing Time incorrectly. I have my TZ set on the UF server, splunk server and in my preferences as EST but I am getting this: ... See more...
Hi,   Rather new to splunk. I got some logs ingested but they are showing Time incorrectly. I have my TZ set on the UF server, splunk server and in my preferences as EST but I am getting this: 12/11/23 8:35:24.000 AM   2023-12-11T13:35:24+00:00 routerXXXXXX   If I look at the field _time I have: 2023-12-11T08:35:24.000-05:00 I suspect the source host or I need a props.conf to fix?
How can you determine the number of correlation searches instances of Splunk Security can handle? For both Splunk Enterprise on prem and Splunk Enterprise in the Cloud. And yes i am taling about acti... See more...
How can you determine the number of correlation searches instances of Splunk Security can handle? For both Splunk Enterprise on prem and Splunk Enterprise in the Cloud. And yes i am taling about active and non-active correlation searches in Splunk. Please also let me know if you want to contact me with further questions!     Thanks!
Good afternoon, I want to generate an alert to control the loss of ingestion of the events in the different indexes, but I want to do it that for according to the index that is, the time of ingestio... See more...
Good afternoon, I want to generate an alert to control the loss of ingestion of the events in the different indexes, but I want to do it that for according to the index that is, the time of ingestion varies. That is to say, the windows servers, ingest me almost every minute, on the other hand the antivirus only ingests if it detects something, which can be that it generates at least one event every 5 days. So it does not make sense to check every minute, because the antivirus would generate a lot of noise, and not every 2 days, because in the case of losing communication with the forwarder I would realize 2 days later, and the service would not work efficiently. Does anyone know if it is possible to generate this alert, without having to generate an alert by index? Thank you very much in advance!
Hi, I want to create the panel (table) to monitor the todays data vs yesterdays log data as below.  Please could you help ? how to get the missed data Current SPL: basesearch | stats count as Co... See more...
Hi, I want to create the panel (table) to monitor the todays data vs yesterdays log data as below.  Please could you help ? how to get the missed data Current SPL: basesearch | stats count as Count_Today by User | appendcols [ basesearch | stats count as Count_Yesterday by User] | eval Missing=abs(round(VOLUMELASTWEEK-VOLUMETODAY)) | table User Count_Today Count_Yesterday Missing Expected Result: User Count_Today Count_Yesterday Missing Missed File Name ABC 5 4 1 abc*  
HI, (excuse me, my english is not so good) i'm trying use curl on Splunkcloud but doesnt work, i'm receiving timeout. If i try curl via cmd on my computer or splunk forwader using the same command i ... See more...
HI, (excuse me, my english is not so good) i'm trying use curl on Splunkcloud but doesnt work, i'm receiving timeout. If i try curl via cmd on my computer or splunk forwader using the same command i have success but splunk Cloud i doesnt have success. Command (App webtools): | curl uri=https://f*****r:7443/api/v2/monitor/system/ha-statistics?access_token=g4**** Error: HTTPSConnectionPool(host='f*****r', port=7443): Max retries exceeded with url: /api/v2/monitor/system/ha-statistics?access_token=g4******* (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f22bfa13210>, 'Connection to fort-01.blu.com.br timed out. (connect timeout=60)'))
Observability Unveiled: Navigating OpenTelemetry's Framework and Deployment Options A recent Tech Talk, Starting With Observability: OpenTelemetry Best Practices explored the foundational technol... See more...
Observability Unveiled: Navigating OpenTelemetry's Framework and Deployment Options A recent Tech Talk, Starting With Observability: OpenTelemetry Best Practices explored the foundational technology and framework of OpenTelemetry, focusing on its role in enabling observability practices and its rapid adoption across various industries. It emphasizes the value of deploying the OpenTelemetry collector and the recommended modes of deployment, such as Agent mode and Gateway mode. Hear from Splunk’s Observability Practitioner Director, Greg Leffler, as he delves into tips and tricks for using OpenTelemetry, understanding the deployment options, and choosing the appropriate deployment model based on the specific needs of the environment.   Exploring OpenTelemetry: An Introduction to Observability Understanding OpenTelemetry: A Framework for Observability Learn about OpenTelemetry, a foundational technology used for observability, its components, integrations, and benefits for monitoring and instrumentation across various platforms and languages. OpenTelemetry, a buzzword that has caught the attention of many, is the focus of this edition of Splunk's Tech Talks. The session delves into the foundational technology and framework that OpenTelemetry offers for observability. It is designed to capture distributed traces, metrics, logs, and more, providing a standard way to enrich data. OpenTelemetry also stands out for its flexibility and lack of vendor lock-in, offering users full control over their telemetry data. The webinar highlights the importance of OpenTelemetry, emphasizing its role in enabling observability practices and its rapid adoption across various industries. According to the speaker, a significant number of organizations are already embracing observability, recognizing its value and the need for dedicated experts in this field. The session also addresses the process of getting started with OpenTelemetry, emphasizing the significance of deploying the OpenTelemetry collector and the recommended modes of deployment, such as Agent mode and Gateway mode.   Implementing OpenTelemetry: Starting Small and Necessary Configurations Getting Started With Splunk and OpenTelemetry: Installation and Configuration Guide Learn how to easily start using Splunk with OpenTelemetry, whether you're a Splunk customer or not, by following the installation and configuration steps. When implementing OpenTelemetry, it is crucial to start small and gradually expand a deployment. By beginning with one service or a specific environment, it allows for a better understanding of the benefits and facilitates easier configuration adjustments. Additionally, it is important to ensure the necessary extensions are enabled for seamless troubleshooting and data processing. Extensions such as health checks, zpages, and batch are essential for monitoring the performance of data pipelines. Moreover, log collection via the Filelog receiver can be considered to reduce the number of needed agents. By following these steps, the implementation of OpenTelemetry can be streamlined and optimized for effective observability. It's also worth noting that the majority of business cases involve the deployment of OpenTelemetry in Agent mode, which is the most common and recommended approach for collecting host metric data and forwarding application data to the observability backend. However, in complex environments or where scalability and network traffic need to be managed, deploying the collector in gateway mode might be more suitable.   Tips and Tricks for Using OpenTelemetry   When using OpenTelemetry, it is essential to consider the deployment mode that best suits your environment. The most common mode is the Agent mode, which is deployed onto every machine to collect host metric data and forward application data to the observability backend. However, for complex environments with potential network constraints or scalability concerns, the Gateway mode is a viable option. In Gateway mode, the agent can still run on every machine but it would then direct data to a gateway machine before sending it to the observability backend, addressing issues related to network traffic and data volume. Additionally, in cases where the collector is not required, such as in platform-as-a-service systems, applications can directly emit data to endpoints without the need for a collector. Understanding the deployment options and choosing the appropriate mode based on the specific needs of the environment is crucial for effective implementation of OpenTelemetry.   Understanding OpenTelemetry Collector Deployment Modes Understanding the OpenTelemetry Collector and Ecosystem Explore the functionalities of the OpenTelemetry collector, including receivers, processors, extensions, and exporters, enabling efficient data collection and integration with various formats and destinations. The OpenTelemetry collector offers two deployment modes: Agent mode, Gateway mode. You can also use OpenTelemetry without the collector (No Collector mode). In Agent mode, the collector is deployed on every machine to collect host metric data and application data, forwarding it to the observability backend. This mode is recommended for most common environments. On the other hand, Gateway mode involves running the agent on every machine but instead of sending data directly to the observability backends, sending it to a gateway machine, which then communicates with the observability backend. Gateway mode is suitable for complex environments, large-scale deployments, and where network traffic and overall performance of the observability infrastructure need careful consideration. Alternatively, in scenarios where the collector is not required, such as in platform as a service systems, applications can directly emit data to endpoints without the need for a collector. This 'No Collector' mode is ideal for simple applications that require minimal instrumentation. Understanding these deployment modes is crucial for optimizing the performance and efficiency of the OpenTelemetry collector in different deployment scenarios. Ready to Watch the Full Recording? Starting With Observability: OpenTelemetry Best Practices Watch the Replay Exploring Key Features of OpenTelemetry Exploring Zpages: A Hidden Gem in OpenTelemetry Collector Discover the power of Zpages in OpenTelemetry Collector for monitoring and troubleshooting pipelines with ease. OpenTelemetry offers a range of powerful features designed to enhance observability and streamline the collection of crucial data. One noteworthy feature is the zpages extension, which provides valuable troubleshooting insights. By enabling the zpages extension during the setup of the OpenTelemetry pipeline, users gain access to configz, statsz, rpcz, and tracez. These components offer real-time visibility into the internal workings of the collector, simplifying the troubleshooting process and providing essential performance metrics. The OpenTelemetry pipeline is a core component that supports receivers, processors, and exporters. Receivers are capable of accepting data in various formats, including OTLP, Jaeger, Prometheus, and more, ensuring flexibility in data ingestion. Processors allow for data manipulation, such as sampling, batching, and filtering, offering extensive customization options. Exporters then facilitate the transfer of data out of the collector, enabling seamless integration with observability backends. Furthermore, OpenTelemetry promotes both automatic and manual instrumentation.   Getting Started with OpenTelemetry Getting Started With Splunk and OpenTelemetry: Installation and Configuration Guide Learn how to easily start using Splunk with OpenTelemetry, whether you're a Splunk customer or not, by following the installation and configuration steps. To begin with, automatic instrumentation should be the starting point for any OpenTelemetry deployment. It eliminates the need to understand OpenTelemetry in significant depth, making it a suitable option for most use cases. However, if automatic instrumentation is not available for certain languages or frameworks, manual instrumentation can be added as needed. For Splunk customers, using resources such as the Cloud Native Computing Foundation Slack and Splunk Professional Services is highly recommended. The Slack channel provides real-time access to OpenTelemetry experts for specific problem-solving, and Splunk Professional Services can offer valuable support and guidance, with assigned experts on Splunk and OpenTelemetry available. Joining the Cloud Native Computing Foundation Slack is essential for gathering insights and assistance related to OpenTelemetry. The community-focused program allows users to engage with knowledgeable individuals and stay updated on the latest developments. It's crucial to initiate an OpenTelemetry deployment as soon as possible, as it provides an opportunity to gain experience and familiarity with the system.   Deploying the Collector: Platforms and Steps Getting Started With Splunk Observability Cloud: Deploying the OpenTelemetry Collector Learn how to deploy the OpenTelemetry Collector in Splunk Observability Cloud and configure it using the provided configuration files. The OpenTelemetry collector can be deployed on various platforms, including Linux, Windows, Kubernetes, and EC2. The deployment can also be carried out in different modes, such as agent or gateway. It is recommended to use the agent mode for deployment. In Splunk Observability Cloud, the process begins with clicking on the 'Add Integration' option and selecting OpenTelemetry as the integration of choice. This initiates a wizard to set up the collector. The installation process requires the use of cURL to download the setup script, which then determines the realm of the observability cloud install and the access token to be used. Additionally, the Java zero-touch instrumentation can be enabled during the deployment process. Once the deployment is completed, the configuration file for the collector is located at /etc/otel/collector/config.yaml, and the environment variables are specified at /etc/otel/collector/splunk-otel-collector.conf.   Configuring the Splunk OpenTelemetry Collector Getting Started With Splunk Observability Cloud: Deploying the OpenTelemetry Collector Learn how to deploy the OpenTelemetry Collector in Splunk Observability Cloud and configure it using the provided configuration files. The configuration of the Splunk OpenTelemetry Collector is an essential aspect of setting up and optimizing your observability platform. The collector relies on two key configuration files, which hold critical information about the collector's operation and behavior. The configuration file for the collector is located at /etc/otel/collector/config.yaml, while the environment variables are specified in /etc/otel/collector/splunk-otel-collector.conf. These files play a pivotal role in determining how the collector runs, the pipeline structure, and the settings for extensions and environment variables. Making changes to these configuration files is a straightforward process. Any modifications to the configuration files must be followed by a restart of the collector to ensure the changes take effect. It is important to note that the OpenTelemetry Auto Instrumentation package can also be installed, which automatically updates the ld.so.preload file, enabling automatic instrumentation of Java applications by simply restarting them.   Exploring OpenTelemetry Features: Enabling zpages Discover the power of Zpages in OpenTelemetry Collector for monitoring and troubleshooting pipelines with ease. Enabling zpages in the OpenTelemetry collector provides valuable insights into the system's performance and operation. These zpages offer a comprehensive view of the collector's inner workings and facilitate efficient monitoring and troubleshooting. Introduction to zpages: Zpages are an essential feature of the OpenTelemetry collector, allowing users to gain visibility into various aspects of the system. They offer detailed information about the collector's configuration, pipeline, extensions, and traces, enabling users to better understand the behavior of the collector. Different types of zpages: There are several types of zpages, each serving a specific purpose. These include the config zpage, pipeline zpage, extensions zpage, feature zpage, and trace zpage. Each type provides distinct insights into the functioning of the OpenTelemetry collector, allowing for comprehensive analysis and monitoring.   Conclusion In conclusion, OpenTelemetry plays a pivotal role in enabling observability practices, offering a standard way to enrich data and providing flexibility without vendor lock-in. The deployment of the OpenTelemetry collector, with a focus on agent mode and gateway mode, is crucial for effective data collection and forwarding to the observability backend. The deployment process involves utilizing cURL to download the setup script, determining the realm of the observability cloud install, and configuring the access token. Related Tech Talk OpenTelemetry: What’s Next. Logs, Profiles, and More. Watch the Replay  
Hi Cannot create a ticket in official support. Required combo "Select Entitlement" is empty, cannot choose anything, so I cannot continue completing and posting my case. See attached image spl... See more...
Hi Cannot create a ticket in official support. Required combo "Select Entitlement" is empty, cannot choose anything, so I cannot continue completing and posting my case. See attached image splunk_combo.png This happens with both Mozilla Firefox and Google Chrome - both up to date. Please advise Altin Karaulli UnionBank Albania
We are testing the log collection from our paloalto firewalls and seem to have come across a snag when trying to monitor the traffic and threat events. We have the PaloAlto addon and app installed an... See more...
We are testing the log collection from our paloalto firewalls and seem to have come across a snag when trying to monitor the traffic and threat events. We have the PaloAlto addon and app installed and it is working fine as the config and system logs are being processed and added to the dashboard. The datamodel accelaration is on but there is still no data. When using the search bar i have been looking for all logs coming in through port 514 as the logs are being send through udp. (source=udp:514) and i can see the system and config logs there too but no other types. I am starting to feel like the issue is with the palo side but i want to make sure that i am not missing something on the splunk side to. Ive gone through the log forwarding form the palo side several times and if its sending the system and config fine, why not the rest? KR
From AppDynamics API, do we have any way to associate the process running on the node to the running application? The API sim/v2/user/machines/<server_id>/processes lists all the process running on t... See more...
From AppDynamics API, do we have any way to associate the process running on the node to the running application? The API sim/v2/user/machines/<server_id>/processes lists all the process running on the node but doesn't expose any relationship with the running application. 
Hi, I am new at Splunk and I'm following the lab in Enriching Data with Lookups, where I'm requested to exclude a value using the Flter Lookup. I have a Lookup definition based on knonwusers.csv In ... See more...
Hi, I am new at Splunk and I'm following the lab in Enriching Data with Lookups, where I'm requested to exclude a value using the Flter Lookup. I have a Lookup definition based on knonwusers.csv In the video it doesn't explain or show any example for this specific field. I have tried the following: user NOT (root OR mail OR apache) user <> (root OR mail OR apache) |inputlookup knownusers.csv |eval user NOT (root OR mail OR apache) And nothing is working. Could you please tell me what am I doing wrong? 
Hi all, I deployed splunk in multi site clustering fashion. everything is good but there are some challenges. There are many indexes  in my case. Some indexes are very important, but they generall... See more...
Hi all, I deployed splunk in multi site clustering fashion. everything is good but there are some challenges. There are many indexes  in my case. Some indexes are very important, but they generally have a small volume and replication is needed for these indexes. On the other hand, there are indexes that are less important but very bulky. Replication is not required for these indexes. My question is what would you suggest to solve this problem. Thank you
I am new to Splunk. I am trying to overwrite the values of a field (eventLevel) that is in Japanese. I created a lookup table to convert these values to English so that the data is more readable. Now... See more...
I am new to Splunk. I am trying to overwrite the values of a field (eventLevel) that is in Japanese. I created a lookup table to convert these values to English so that the data is more readable. Now, how can I see those translated values in the eventLevel field?
Hi  :  As title, After upgrade the Lookup Editor App to v.4.02.  We found the list is limited to 20 records per pages, and it is not convenience for us.    Is there any ways to modified this setti... See more...
Hi  :  As title, After upgrade the Lookup Editor App to v.4.02.  We found the list is limited to 20 records per pages, and it is not convenience for us.    Is there any ways to modified this setting ?   
Hello, I am attempting to compile the extension for VMware monitoring, but consistently encountering failure during the initial step where I need to compile this extension with Maven. Does anyone ha... See more...
Hello, I am attempting to compile the extension for VMware monitoring, but consistently encountering failure during the initial step where I need to compile this extension with Maven. Does anyone have any insights into where the problem might lie? The errors I am encountering are: [INFO] Compiling 11 source files to /home/unx/vmware/vmware-vsphere-monitoring-extension/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] Failure executing javac, but could not parse the error: An annotation processor threw an uncaught exception. Consult the following stack trace for details. java.lang.IllegalAccessError: class lombok.javac.apt.Processor (in unnamed module @0x696174d3) cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x696174d3 at lombok.javac.apt.Processor.init(Processor.java:84) at lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87) at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:141) at lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:53) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.<init>(JavacProcessingEnvironment.java:701) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:828) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:924) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1382) at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1234) at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:916) at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:317) at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:176) at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:82) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:351) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:171) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:163) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:298) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:960) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:293) at org.apache.maven.cli.MavenCli.main(MavenCli.java:196) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347) [INFO] 1 error [INFO] ------------------------------------------------------------- [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 54.163 s [INFO] Finished at: 2023-12-11T10:21:08+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project vsphere-monitoring-extension: Compilation failure [ERROR] Failure executing javac, but could not parse the error: [ERROR] [ERROR] [ERROR] An annotation processor threw an uncaught exception. [ERROR] Consult the following stack trace for details. [ERROR] java.lang.IllegalAccessError: class lombok.javac.apt.Processor (in unnamed module @0x696174d3) cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x696174d3 [ERROR] at lombok.javac.apt.Processor.init(Processor.java:84) [ERROR] at lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87) [ERROR] at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:141) [ERROR] at lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:53) [ERROR] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.<init>(JavacProcessingEnvironment.java:701) [ERROR] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:828) [ERROR] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:924) [ERROR] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) [ERROR] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1382) [ERROR] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1234) [ERROR] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:916) [ERROR] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:317) [ERROR] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:176) [ERROR] at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:82) [ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) [ERROR] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:568) [ERROR] at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554) [ERROR] at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161) [ERROR] at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605) [ERROR] at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) [ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute(MojoExecutor.java:351) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:215) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:171) [ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:163) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) [ERROR] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56) [ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:298) [ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192) [ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105) [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:960) [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:293) [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:196) [ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ERROR] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) [ERROR] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [ERROR] at java.base/java.lang.reflect.Method.invoke(Method.java:568) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406) [ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347) [ERROR] [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException My friend advised me to try to add following dependencie to  pom.xml <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>1.18.26</version> <scope>provided</scope> </dependency> So, I followed the instructions, and it seems like the entire process is progressing a bit further before halting at the testing stage. Now, I find myself stuck at this point: [INFO] Scanning for projects... [INFO] [INFO] ------< com.appdynamics.extensions:vsphere-monitoring-extension >------- [INFO] Building vsphere-monitoring-extension 3.0.2 [INFO] --------------------------------[ jar ]--------------------------------- Downloading from github-maven-repo: https://github.com/Appdynamics/maven-repo/raw/master/releases/org/projectlombok/lombok/1.18.26/lombok-1.18.26.pom Downloading from central: https://repo.maven.apache.org/maven2/org/projectlombok/lombok/1.18.26/lombok-1.18.26.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/projectlombok/lombok/1.18.26/lombok-1.18.26.pom (1.5 kB at 8.8 kB/s) Downloading from github-maven-repo: https://github.com/Appdynamics/maven-repo/raw/master/releases/org/projectlombok/lombok/1.18.26/lombok-1.18.26.jar Downloading from central: https://repo.maven.apache.org/maven2/org/projectlombok/lombok/1.18.26/lombok-1.18.26.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/projectlombok/lombok/1.18.26/lombok-1.18.26.jar (2.0 MB at 10.0 MB/s) [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ vsphere-monitoring-extension --- [INFO] Deleting /home/unx/vmware/vmware-vsphere-monitoring-extension/target [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ vsphere-monitoring-extension --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ vsphere-monitoring-extension --- [INFO] Compiling 11 source files to /home/unx/vmware/vmware-vsphere-monitoring-extension/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ vsphere-monitoring-extension --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ vsphere-monitoring-extension --- [INFO] Compiling 3 source files to /home/unx/vmware/vmware-vsphere-monitoring-extension/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ vsphere-monitoring-extension --- Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.0.9/maven-plugin-api-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.0.9/maven-plugin-api-2.0.9.pom (1.5 kB at 28 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven/2.0.9/maven-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven/2.0.9/maven-2.0.9.pom (19 kB at 300 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/8/maven-parent-8.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/8/maven-parent-8.pom (24 kB at 377 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/apache/4/apache-4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/apache/4/apache-4.pom (4.5 kB at 78 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.pom (3.0 kB at 51 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.pom (2.5 kB at 43 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/maven-surefire-common/2.12.4/maven-surefire-common-2.12.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/maven-surefire-common/2.12.4/maven-surefire-common-2.12.4.pom (5.5 kB at 102 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-annotations/3.1/maven-plugin-annotations-3.1.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-annotations/3.1/maven-plugin-annotations-3.1.pom (1.6 kB at 27 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools/3.1/maven-plugin-tools-3.1.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools/3.1/maven-plugin-tools-3.1.pom (16 kB at 270 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact/2.0.9/maven-artifact-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact/2.0.9/maven-artifact-2.0.9.pom (1.6 kB at 31 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.pom (3.1 kB at 57 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/3.2/plexus-3.2.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/3.2/plexus-3.2.pom (19 kB at 329 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/sonatype/spice/spice-parent/17/spice-parent-17.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/sonatype/spice/spice-parent/17/spice-parent-17.pom (6.8 kB at 123 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/sonatype/forge/forge-parent/10/forge-parent-10.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/sonatype/forge/forge-parent/10/forge-parent-10.pom (14 kB at 247 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.pom (2.7 kB at 50 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.0.9/maven-settings-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.0.9/maven-settings-2.0.9.pom (2.1 kB at 40 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.0.9/maven-model-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.0.9/maven-model-2.0.9.pom (3.1 kB at 64 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.0.9/maven-profile-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.0.9/maven-profile-2.0.9.pom (2.0 kB at 34 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.0.9/maven-artifact-manager-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.0.9/maven-artifact-manager-2.0.9.pom (2.7 kB at 48 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.0.9/maven-repository-metadata-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.0.9/maven-repository-metadata-2.0.9.pom (1.9 kB at 33 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.0.9/maven-plugin-registry-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.0.9/maven-plugin-registry-2.0.9.pom (2.0 kB at 38 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/2.0.9/maven-core-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/2.0.9/maven-core-2.0.9.pom (7.8 kB at 134 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.0.9/maven-plugin-parameter-documenter-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.0.9/maven-plugin-parameter-documenter-2.0.9.pom (2.0 kB at 36 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.pom (1.8 kB at 38 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting/2.0.9/maven-reporting-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting/2.0.9/maven-reporting-2.0.9.pom (1.5 kB at 31 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.0.9/maven-error-diagnostics-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.0.9/maven-error-diagnostics-2.0.9.pom (1.7 kB at 35 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.0.9/maven-plugin-descriptor-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.0.9/maven-plugin-descriptor-2.0.9.pom (2.1 kB at 41 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.0.9/maven-monitor-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.0.9/maven-monitor-2.0.9.pom (1.3 kB at 25 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/2.0.9/maven-toolchain-2.0.9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/2.0.9/maven-toolchain-2.0.9.pom (3.5 kB at 61 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.pom (17 kB at 293 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.3/maven-common-artifact-filters-1.3.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.3/maven-common-artifact-filters-1.3.pom (3.7 kB at 69 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/12/maven-shared-components-12.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-components/12/maven-shared-components-12.pom (9.3 kB at 176 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/13/maven-parent-13.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-parent/13/maven-parent-13.pom (23 kB at 444 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/apache/6/apache-6.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/apache/6/apache-6.pom (13 kB at 246 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-container-default-1.0-alpha-9.pom (1.2 kB at 25 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.0.9/maven-plugin-api-2.0.9.jar Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/maven-surefire-common/2.12.4/maven-surefire-common-2.12.4.jar Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-api/2.0.9/maven-plugin-api-2.0.9.jar (13 kB at 248 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.3/maven-common-artifact-filters-1.3.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-common-artifact-filters/1.3/maven-common-artifact-filters-1.3.jar (31 kB at 272 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar (35 kB at 251 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact/2.0.9/maven-artifact-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar (118 kB at 811 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/maven-surefire-common/2.12.4/maven-surefire-common-2.12.4.jar (263 kB at 1.5 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.0.9/maven-settings-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0.8/plexus-utils-3.0.8.jar (232 kB at 1.4 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.0.9/maven-profile-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.1/commons-lang3-3.1.jar (316 kB at 1.7 MB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.0.9/maven-model-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.0.9/maven-project-2.0.9.jar (122 kB at 618 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.0.9/maven-artifact-manager-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact/2.0.9/maven-artifact-2.0.9.jar (89 kB at 417 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.0.9/maven-plugin-registry-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.0.9/maven-settings-2.0.9.jar (49 kB at 227 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/2.0.9/maven-core-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.0.9/maven-profile-2.0.9.jar (35 kB at 162 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.0.9/maven-plugin-parameter-documenter-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-model/2.0.9/maven-model-2.0.9.jar (87 kB at 356 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.0.9/maven-artifact-manager-2.0.9.jar (58 kB at 234 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.0.9/maven-repository-metadata-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.0.9/maven-plugin-registry-2.0.9.jar (29 kB at 106 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.0.9/maven-error-diagnostics-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.0.9/maven-plugin-parameter-documenter-2.0.9.jar (21 kB at 76 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.0.9/maven-plugin-descriptor-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-core/2.0.9/maven-core-2.0.9.jar (160 kB at 578 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.0.9/maven-monitor-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.0.9/maven-repository-metadata-2.0.9.jar (25 kB at 81 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/2.0.9/maven-toolchain-2.0.9.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.0.9/maven-reporting-api-2.0.9.jar (10 kB at 34 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-annotations/3.1/maven-plugin-annotations-3.1.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.0.9/maven-error-diagnostics-2.0.9.jar (14 kB at 42 kB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.0.9/maven-monitor-2.0.9.jar (10 kB at 31 kB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.0.9/maven-plugin-descriptor-2.0.9.jar (37 kB at 112 kB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/plugin-tools/maven-plugin-annotations/3.1/maven-plugin-annotations-3.1.jar (14 kB at 40 kB/s) Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-toolchain/2.0.9/maven-toolchain-2.0.9.jar (38 kB at 108 kB/s) [INFO] Surefire report directory: /home/unx/vmware/vmware-vsphere-monitoring-extension/target/surefire-reports Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-junit4/2.12.4/surefire-junit4-2.12.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-junit4/2.12.4/surefire-junit4-2.12.4.pom (2.4 kB at 51 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-providers/2.12.4/surefire-providers-2.12.4.pom Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-providers/2.12.4/surefire-providers-2.12.4.pom (2.3 kB at 44 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-junit4/2.12.4/surefire-junit4-2.12.4.jar Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/surefire/surefire-junit4/2.12.4/surefire-junit4-2.12.4.jar (37 kB at 710 kB/s) ------------------------------------------------------- T E S T S ------------------------------------------------------- Running com.appdynamics.monitors.VMWare.VMWareMonitorTest SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.523 sec Running com.appdynamics.monitors.VMWare.collectors.HostMetricCollectorTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.219 sec <<< FAILURE! initializationError(com.appdynamics.monitors.VMWare.collectors.HostMetricCollectorTest) Time elapsed: 0.004 sec <<< ERROR! org.objenesis.ObjenesisException: java.lang.reflect.InvocationTargetException at org.objenesis.instantiator.sun.SunReflectionFactoryHelper.newConstructorForSerialization(SunReflectionFactoryHelper.java:55) at org.objenesis.instantiator.sun.SunReflectionFactoryInstantiator.<init>(SunReflectionFactoryInstantiator.java:38) at org.objenesis.strategy.StdInstantiatorStrategy.newInstantiatorOf(StdInstantiatorStrategy.java:58) at org.objenesis.ObjenesisBase.getInstantiatorOf(ObjenesisBase.java:91) at org.powermock.reflect.internal.WhiteboxImpl.newInstance(WhiteboxImpl.java:259) at org.powermock.reflect.Whitebox.newInstance(Whitebox.java:139) at org.powermock.tests.utils.impl.AbstractTestSuiteChunkerImpl.getPowerMockTestListenersLoadedByASpecificClassLoader(AbstractTestSuiteChunkerImpl.java:95) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:174) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:48) at org.powermock.tests.utils.impl.AbstractTestSuiteChunkerImpl.createTestDelegators(AbstractTestSuiteChunkerImpl.java:108) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.<init>(JUnit4TestSuiteChunkerImpl.java:71) at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.<init>(AbstractCommonPowerMockRunner.java:36) at org.powermock.modules.junit4.PowerMockRunner.<init>(PowerMockRunner.java:34) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:250) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.objenesis.instantiator.sun.SunReflectionFactoryHelper.newConstructorForSerialization(SunReflectionFactoryHelper.java:45) ... 35 more Caused by: java.lang.IllegalAccessError: class jdk.internal.reflect.ConstructorAccessorImpl loaded by org.powermock.core.classloader.MockClassLoader @7b139eab cannot access jdk/internal/reflect superclass jdk.internal.reflect.MagicAccessorImpl at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.powermock.core.classloader.MockClassLoader.loadUnmockedClass(MockClassLoader.java:262) at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:206) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass1(DeferSupportingClassLoader.java:89) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:79) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.powermock.core.classloader.MockClassLoader.loadUnmockedClass(MockClassLoader.java:262) at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:206) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass1(DeferSupportingClassLoader.java:89) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:79) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.System$2.defineClass(System.java:2303) at java.base/jdk.internal.reflect.ClassDefiner.defineClass(ClassDefiner.java:66) at java.base/jdk.internal.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:401) at java.base/jdk.internal.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:395) at java.base/java.security.AccessController.doPrivileged(AccessController.java:318) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:394) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:112) at java.base/jdk.internal.reflect.ReflectionFactory.generateConstructor(ReflectionFactory.java:463) at java.base/jdk.internal.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:376) at jdk.unsupported/sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:100) ... 40 more Running com.appdynamics.monitors.VMWare.VMWareMonitorTaskTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.069 sec <<< FAILURE! initializationError(com.appdynamics.monitors.VMWare.VMWareMonitorTaskTest) Time elapsed: 0.001 sec <<< ERROR! org.objenesis.ObjenesisException: java.lang.reflect.InvocationTargetException at org.objenesis.instantiator.sun.SunReflectionFactoryHelper.newConstructorForSerialization(SunReflectionFactoryHelper.java:55) at org.objenesis.instantiator.sun.SunReflectionFactoryInstantiator.<init>(SunReflectionFactoryInstantiator.java:38) at org.objenesis.strategy.StdInstantiatorStrategy.newInstantiatorOf(StdInstantiatorStrategy.java:58) at org.objenesis.ObjenesisBase.getInstantiatorOf(ObjenesisBase.java:91) at org.powermock.reflect.internal.WhiteboxImpl.newInstance(WhiteboxImpl.java:259) at org.powermock.reflect.Whitebox.newInstance(Whitebox.java:139) at org.powermock.tests.utils.impl.AbstractTestSuiteChunkerImpl.getPowerMockTestListenersLoadedByASpecificClassLoader(AbstractTestSuiteChunkerImpl.java:95) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:174) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.createDelegatorFromClassloader(JUnit4TestSuiteChunkerImpl.java:48) at org.powermock.tests.utils.impl.AbstractTestSuiteChunkerImpl.createTestDelegators(AbstractTestSuiteChunkerImpl.java:108) at org.powermock.modules.junit4.common.internal.impl.JUnit4TestSuiteChunkerImpl.<init>(JUnit4TestSuiteChunkerImpl.java:71) at org.powermock.modules.junit4.common.internal.impl.AbstractCommonPowerMockRunner.<init>(AbstractCommonPowerMockRunner.java:36) at org.powermock.modules.junit4.PowerMockRunner.<init>(PowerMockRunner.java:34) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:250) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.objenesis.instantiator.sun.SunReflectionFactoryHelper.newConstructorForSerialization(SunReflectionFactoryHelper.java:45) ... 35 more Caused by: java.lang.IllegalAccessError: class jdk.internal.reflect.ConstructorAccessorImpl loaded by org.powermock.core.classloader.MockClassLoader @3fc08eec cannot access jdk/internal/reflect superclass jdk.internal.reflect.MagicAccessorImpl at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.powermock.core.classloader.MockClassLoader.loadUnmockedClass(MockClassLoader.java:262) at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:206) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass1(DeferSupportingClassLoader.java:89) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:79) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.powermock.core.classloader.MockClassLoader.loadUnmockedClass(MockClassLoader.java:262) at org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:206) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass1(DeferSupportingClassLoader.java:89) at org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:79) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.System$2.defineClass(System.java:2303) at java.base/jdk.internal.reflect.ClassDefiner.defineClass(ClassDefiner.java:66) at java.base/jdk.internal.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:401) at java.base/jdk.internal.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:395) at java.base/java.security.AccessController.doPrivileged(AccessController.java:318) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:394) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:112) at java.base/jdk.internal.reflect.ReflectionFactory.generateConstructor(ReflectionFactory.java:463) at java.base/jdk.internal.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:376) at jdk.unsupported/sun.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:100) ... 40 more Results : Tests in error: initializationError(com.appdynamics.monitors.VMWare.collectors.HostMetricCollectorTest): java.lang.reflect.InvocationTargetException initializationError(com.appdynamics.monitors.VMWare.VMWareMonitorTaskTest): java.lang.reflect.InvocationTargetException Tests run: 3, Failures: 0, Errors: 2, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7.577 s [INFO] Finished at: 2023-12-11T10:27:30+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project vsphere-monitoring-extension: There are test failures. [ERROR] [ERROR] Please refer to /home/unx/vmware/vmware-vsphere-monitoring-extension/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Hi, Can someone please assist me with the steps/commands that need to be performed when pointing existing Splunk components (Deployment Server, Search Heads, Heavy Forwarder, Indexer) to a different... See more...
Hi, Can someone please assist me with the steps/commands that need to be performed when pointing existing Splunk components (Deployment Server, Search Heads, Heavy Forwarder, Indexer) to a different existing License Server? We currently have two separate environments with their own License Servers, now this is all being merged into one license. So, one of the environments needs to point to the other existing License Server where the new license will be installed. Thanks
Hi I am trying to see for a ticket that is not assigned to an analyst for the last 15 mins from the time of arrival. I have only the timestamp system_updated meaning when ever there is any change in... See more...
Hi I am trying to see for a ticket that is not assigned to an analyst for the last 15 mins from the time of arrival. I have only the timestamp system_updated meaning when ever there is any change in the INC the timestamping gets updated for that event. index="servicenow" INC* sourcetype="snow:incident" |where assigned_to = "" |rename sys_updated_on as earliest |eval date = strptime(earliest, "%Y-%m-%d %H:%M:%S.%3N") | eval start=strftime(strptime(earliest, "%Y-%m-%d %H:%M:%S.%2N") + 1, "%Y-%m-%d %H:%M:%S.%2N") | eval end=strftime(strptime(earliest, "%Y-%m-%d %H:%M:%S.%2N") + 900, "%Y-%m-%d %H:%M:%S.%2N") |table ticket_number start end So here I have taken the time when the assigned to field was empty and that is the iNC created time as well. From that next second to the 15 min I need to know the series of events with the help of  start and end values.  When I do so I am not able to see any events. Please help
Hello, two quick questions regarding the Splunk Add-on for JBoss and the Splunk Add-on for JMX: The documentation says that both TA's require Oracle JDK or openJDK. Given the documentation, I'm... See more...
Hello, two quick questions regarding the Splunk Add-on for JBoss and the Splunk Add-on for JMX: The documentation says that both TA's require Oracle JDK or openJDK. Given the documentation, I'm assuming that there is no possibility to run the TA's with another JDK distribution such as JDK variants of Azul (Zulu Prime aka Zing or Zulu) - could someone here confirm this? If it's indeed not possible, is it sufficient to only have the openJDK on the Heavy Forwarder? I would assume yes since the doc says: "Install Java Runtime 1.7 or later on the same machine as the Splunk Add-on for JBoss. Note: You need to use the OpenJDK Java Runtime or Oracle Java Runtime."
Hello i am getting this below error on the linux server and can't find the nmon performance data on the server, can some one please help? how to rectify on it? 12-11-2023 08:39:48.203 +0100 INFO  l... See more...
Hello i am getting this below error on the linux server and can't find the nmon performance data on the server, can some one please help? how to rectify on it? 12-11-2023 08:39:48.203 +0100 INFO  loader [8843 MainThread] - SPLUNK_MODULE_PATH environment variable not found - defaulting to /splunk/splunkforwarder/etc/modules