TechZen - Zenoss User Community Forums

Thanks for doing the legwork and trying to figure this out. Setting up a query variable to pull just the device id's still isn't possible with the way the metric data is saved by Zenoss 6 and the existing OpenTSDB api endpoints.  Even with the api/suggest ...

I did some asking around on the subject, and there was a valid reason initially (though I haven't been able to determine what that reason was). Today, the reason is that all of the code that touches performance data expects that format. This isn't user-configurable ...

Just following up on my last response. Is there a technical requirement to have the device id in the metric name?  If no technical requirement is needed, is there a config setting or perhaps some sort of code change that I can do to remove the device ...

Thanks for the response Michael. Unfortunately there is no raw query mode for the OpenTSDB data source in Grafana.  I'm stuck with their query editor. We might have to look into an alternative solution for our monitoring. Grafana has been an integral ...

I did some quick searching for some sort of "raw query" mode in Grafana's docs, and I came up with this link: https://grafana.com/docs/grafana/latest/features/datasources/influxdb/#text-editor-mode-raw As a caveat, my firsthand knowledge of Grafana ...

Thanks for the quick response Michael.  I'm using Grafana's Query editor to build the query and show the data on a line chart.  I'm not exactly sure how to translate the info you provided into this query form.  For example, I'd like to show the 5 min ...

I tweaked the report down to a mere two devices so that I could share the payload without redacting 23 host names.  I came up with this: {"start":1580947368865,"end":1581033768865,"series":true,"downsample":"5m-avg","tags":{},"returnset":"EXACT","metrics":[{"metric":"redacted-01/uptime_laLoadInt15","id":"bjyDKLB9Ja","rate":false,"rateOptions":{},"aggregator":"avg","tags":{"key":["Devices/redacted-01"]},"name":"redacted-01 ...

Mike, The OpenTSDB query format won't allow you to use wildcards in the metric name, but you can supply multiple metrics in a single query.  To confirm this, I made a sample multi-graph report on a test instance, and configured it to throw all the graphed ...

Due to security requirements, we're forced to migrate from Zenoss 4 to Zenoss 6. Currently with Zenoss 4 we have a Graphite instance that reads the RRD files which is added as a datasource in Grafana to create dashboards. With Graphite I can create a ...

In Zenoss 4.2 and prior, you could get away with using zensendevent remotely.  After Zenoss was "dockerized" (version 5.0 and up), zensendevent will only work from within a container. If you need non-Zenoss devices to send events into your Zenoss instance, ...

​ Hi Jane   We use zensendevent on all our monitored nodes to send alerts back to zenoss, the command does work on the container itself but when attempted from any of the monitored nodes we get socket.error: [Errno 111] ...

Hi Larry, Thanks for all your recent posts - especially those with ANSWERS! It's a big ask, but if you can document some of your migration steps, I think there are many who would appreciate them. I have helped a couple of people do the move but it has ...