#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Create a prometheus compliant exporter for domino stats.

Domino 10 added filesystem based exporter of stats for usage with external monitoring solutions.

The de-facto standard for monitoring is becoming Prometheus with it's common format for exporting an application's stats.

See, https://prometheus.io/docs/instrumenting/writing_exporters/

I'd like to have a new domino server tasks that can be started on the server and provides Prometheus compliant data from Domino's statistics.

It should start a tiny http server and provide resources for scraping by a prometheus or micrologging server.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 3 2020
  • Needs review
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    7 May 09:46pm

    Daniele Vistalli and myself have been looking for a way to allow another server to pull instead of push statistics.

    The code is already there as Daniele found out.

    Our shared idea was to put the file into the domino/html directory and serve it from there.

    We found the following documentation. But it turns out the file is always appended and not overwritten.

    You can specify a data like in this example. So that a local application. could take an remove it.

    But if you set a static file, this will grow forever. The file seems to be created without the overwrite option if already exists.

    Having a switch to turn that off, would help us to use it with cool need monitoring applications like Prometheus !

    https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-1255

    Panopta is using the option to create a file per interval and will probably remove it on it's own.

    We don't want a local logic.

    Pushing or pulling the data is a great way!

    Of course we have to take care about authentication. But we can protect HTML files...

    This would be a small cool change for a FP :-)

    And maybe having it directly served from the HTTP task in the next release?

    I could build a DSAPI to serve and remove it. But having it out of the box working to be used for Prometheus and other tools out of the box would be awesome!

    Daniel Nashed

    https://docs.panopta.com/articles/#!online-help/integrate-with-domino/q/domino/qid/7838/qp/1

    STATPUB_ENABLE=1

    STATPUB_URI=file:///../../usr/share/panopta-agent/incoming/dominostats_$Timestamp$

    STATPUB_HEADERS=Content-type: application/json

    STATPUB_DATA_HEAD={"agent_payload_version": 1.0, "plugin_textkey": "com.pnp-hcl.dominostats", "plugin_category_name": "Domino Statistics", "metrics": [$Newline$

    STATPUB_METRIC_FORMAT={"textkey": "$Name$", "label": "$Name$", "value": $Value$, "unit": "(units)", "timestamp": "$Timestamp$"}

    STATPUB_DELTA_METRIC_FORMAT={"textkey": "Rate.$Name$", "label": "$Name$ Rate", "value": $Value$, "unit": "(units per minute)", "timestamp": "$Timestamp$"}

    STATPUB_METRIC_DELIMITER=,$Newline$

    STATPUB_DATA_TAIL=$Newline$]}