Is there a telegraf plugin which reads snmptraps from snmp manager
Thanks,
Simhadri
I Just came to this question, and in the meantime there is already for a long time the snmp_trap input plugin.
Currently there is no plugin available to listen snmptraps in telegraf. It is an open feature(https://github.com/influxdata/telegraf/issues/4377).
But we have a perl implementation for snmp traps listener, for more you can refer below url
https://metacpan.org/pod/Net::SNMPTrapd
Thanks,
simhadri
Related
I’m doing a performance test using Jmeter and during the test I’m collecting the statistics for backend server performance , for this purpose I use SSHMON sample collector listener in my test plan
https://github.com/tilln/jmeter-sshmon
I have also configured a CSV file path to check the response data received from the server
Issue is that
Data is not recorded in the CSV file and also there is no graph shown for SSHMON listener
In the jemeter logs I can see the following error
java.text.ParseException: Unparseable number: " [2J"
at java.text.NumberFormat.parse(NumberFormat.java:434) ~[?:?]
at nz.co.breakpoint.jmeter.vizualizers.sshmon.SSHMonSampler.generateSamples(SSHMonSampler.java:86) [jmeter-sshmon-1.2.jar:?]
at kg.apc.jmeter.vizualizers.MonitoringResultsCollector.processConnectors(MonitoringResultsCollector.java:215) [jmeter-plugins-cmn-jmeter-0.6.jar:?]
at kg.apc.jmeter.vizualizers.MonitoringResultsCollector.run(MonitoringResultsCollector.java:122) [jmeter-plugins-cmn-jmeter-0.6.jar:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
To verify the SSH configuration and the received data format , I tried to make a SSH connection to the backend server using putty and with same user/pwd and command , I get the data in Putty , please see the attached screenshot
Do I have to change the powershell script to change the format of CPU data, if yes then in which format?
I did not get any info on plugin page.
I would really appreciate if you could provide me some help for this case.
The reason for this issue appears to be related to the terminal control sequence sent
as output of the remote Powershell server application back to the local client,
i.e. the JMeter plugin vs. the Powershell command line.
The characters [2J would be the "Erase in Display" sequence (refer ANSI Escape Codes, e.g. https://en.wikipedia.org/wiki/ANSI_escape_code#CSI_sequences).
In one case those characters would presumably be interpreted by the terminal application displaying the output (e.g. Putty or Cmd window) and the output looks correct.
In the other case however, the control sequence characters are received by the plugin and rejected as unparsable number.
A very similar issue has been reported on the JMeter-Plugins Google Group.
The version 1.3 of the SSHMon plugin uses a different SSH client library which seems to fix the issue according to feedback on the Google Groups thread.
Recommended solution: Upgrade to version 1.3 or later.
Disclaimer: I'm the author of the JMeter SSHMon plugin.
In a fresh install of Jmeter 5.1.1 (on Ubuntu 16.04) some functions are not present:
There is no "Monitor result" in the listener choices
There is no drop-down menu in the "view results tree" to view the response data as html, json, text, xml, etc.
Both are not present at all.
Thanks a lot for any hint on how to get this fixed.
Regards,
Fabianus
Monitor Results has been dropped in JMeter 3.2. You could consider using JMeter PerfMon Plugin for monitoring your application metrics
With regards to View Results Tree listener issue - most probably your installation is incomplete or corrupt, you can try installing missing components using JMeter Plugins Manager
This listener has been removed since version 3.2:
https://jmeter.apache.org/changes_history.html
See related bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60423
I've just upgraded SonarQube from 6.0 to 6.7 LTS running in a CentOS 6 box, and noticed that ElasticSearch (ES) failed to start because the kernel (2.6.32-696.3.1.el6.x86_64) doesn't have seccomp available.
This is officially documented at System call filter check and a correct workaround for systems without this feature is to configure bootstrap.system_call_filter to false in elasticsearch.yml.
The issue here is because Sonar creates the ES configuration at startup, writing in $SONAR_HOME/temp/conf/es/elasticsearch.yml and I haven't found a way to set bootstrap.system_call_filter property.
I tried a natural (undocumented) way introducing sonar.search.bootstrap.system_call_filter and bootstrap.system_call_filter properties in sonar.properties but it doesn't work.
We had the same problem. At first we used the above solution but after searching in the sonar code on github found the place where this setting should be placed:
Edit the sonar.properties file and change the line:
#sonar.search.javaAdditionalOpts=
to
sonar.search.javaAdditionalOpts=-Dbootstrap.system_call_filter=false
For sonarqube docker image, setup additional environment to disable this feature when "docker run":
-e SONAR_SEARCH_JAVAADDITIONALOPTS="-Dbootstrap.system_call_filter=false"
Hi I tried to echo bootstrap.system_call_filter: 'false' to temp/conf/es/elasticsearch.yml, I see the line in that file, but got same error during start of sonarqube 6.7 on centos6.
Has someone tested that with success?
First of all: don't even try to update elasticsearch.yml . SonarQube self-manages its ElasticSearch component config, so any attempt of manual intervention will be harmful. (reminder: the only config file that should ever be modified to operate SonarQube is sonar.properties)
More interestingly regarding that seccomp component:
the seccomp requirement does come from underlying ElasticSearch requirement, and transitively applies to operating SonarQube
if you run SonarQube locally with default config (specifically: default sonar.search.host), then the seccomp check may not be fatal (i.e. just a warning)
if you did override sonar.search.host , then the first thing you should wonder is: does the ElasticSearch JVM really needs to listen on other interfaces than loopback ? (knowing that SonarQube uses ES locally, except with the Data Center Edition). If no good answer to that, then keep sonar.search.host at its default value.
Last but not least, the golden path here is obviously to follow the requirement (i.e. have seccomp available on your OS), even if that involves upgrading to a more recent Linux kernel. And to wrap it all up: we've edited SonarQube Requirements to transparently share this situation.
You could really cheat and edit /${SONAR_HOME}/elasticsearch/bin/elasticsearch.
Add
echo "bootstrap.system_call_filter = 'false'" >>
/${SONAR_HOME}/temp/conf/es/elasticsearch.yml
before the "demonized" variable is set.
I would like rsyslog to forward log messages via HTTP to the service which will process them.
I don't see the exact http-forwarding module for Rsyslog, and I don't want to create another listener on another port just for handling incoming TCP connections, as it would be required with the TCP-output module.
Is it possible or what are the alternatives to process Rsyslog messages by HTTP handler?
Since rsyslog version 8.2202, there is the omhttp module.
Here is an example of what you'd need to implement in /etc/rsyslog.conf:
# include the omhttp module
module(load="omhttp")
# template for each indivdual message, not the format of the resulting batch
template(name="tpl_omhttp_forwarding" type="string" string="%msg%")
# action to send ALL log (files) messages via http
*.* {
action(
type="omhttp"
server="192.1.1.1"
serverport="443"
template="tpl_omhttp_forwarding"
batch="on"
batch.format="jsonarray"
batch.maxsize="10"
action.resumeRetryCount="-1"
)
}
All the action parameters for omhttp, you can find here
NOTE:
Depending on the OS you're using, you may need to build it yourself, or use the repositories here.
For some platforms, there is no omhttp package because of missing or too old dependencies.
There is a new output module called omhttp. I'm looking into it as well, but am having difficulty finding documentation.
https://github.com/rsyslog/rsyslog/issues/3024
Edit: Updated docs are here
https://www.rsyslog.com/doc/v8-stable/configuration/modules/omhttp.html#message-batching
The same script works in jmeter 3.1 but not in jmeter 3.2, why?
Can someone answer that?
EDIT 1:
Open bug for jmeter.
There was a change in SMTP Sampler in jmeter 3.2
Which wasn't tested. I suggest you open a bug to jmeter with a sample.
If you can't post bug I can post it for you if you give sample jmx that doesn't work.
If you can downgrade to Jmeter 3.1 it can work.
I understand this is a fairly big change with no tests but I thought
I'd submit anyway in the hope that someone had some good SMTP tests or
someone was willing to review or even just apply a subset of the
changes.
There's also existing bug reported on SMTP Smapler in Jmeter 3.2.
EDIT
You can download a fix to the issue in jmeter-3.3
I got it to work in Jmeter 3.2.
I got the report stored in a file and gave the path to that file "Attach file(s)" section and its sending email successfully.