Elastic results close to timestamp when no entries close












0















I've been using the following request to get entries close to timestamp, and it works good, until I pick a date that outside of what I have indexed so far. Eg. in the future or in a log that I have stopped indexing some weeks ago.



# Get log close to date
GET _search
{
"query": {
"function_score": {
"functions": [
{
"linear": {
"@timestamp" : {
"origin": "1520627525000",
"scale": "1d",
"decay": 0.01
}
}
}
],
"score_mode" : "multiply",
"boost_mode": "multiply",
"query": {
"bool": {
"must": [
{ "term": { "prospector.type.keyword": "log" } },
{ "term": { "source.keyword": """e:programwdlog.txt""" } },
{ "term": { "host.keyword": "myhost" } }
]
}
}
}
},
"size": 1
}


Then I get a date usually in the beginning of what I indexed, does anyone know how to get better results for when this happens? Or a better way to search for a point in time and get the closest entry.



Some extra information if needed.










share|improve this question



























    0















    I've been using the following request to get entries close to timestamp, and it works good, until I pick a date that outside of what I have indexed so far. Eg. in the future or in a log that I have stopped indexing some weeks ago.



    # Get log close to date
    GET _search
    {
    "query": {
    "function_score": {
    "functions": [
    {
    "linear": {
    "@timestamp" : {
    "origin": "1520627525000",
    "scale": "1d",
    "decay": 0.01
    }
    }
    }
    ],
    "score_mode" : "multiply",
    "boost_mode": "multiply",
    "query": {
    "bool": {
    "must": [
    { "term": { "prospector.type.keyword": "log" } },
    { "term": { "source.keyword": """e:programwdlog.txt""" } },
    { "term": { "host.keyword": "myhost" } }
    ]
    }
    }
    }
    },
    "size": 1
    }


    Then I get a date usually in the beginning of what I indexed, does anyone know how to get better results for when this happens? Or a better way to search for a point in time and get the closest entry.



    Some extra information if needed.










    share|improve this question

























      0












      0








      0








      I've been using the following request to get entries close to timestamp, and it works good, until I pick a date that outside of what I have indexed so far. Eg. in the future or in a log that I have stopped indexing some weeks ago.



      # Get log close to date
      GET _search
      {
      "query": {
      "function_score": {
      "functions": [
      {
      "linear": {
      "@timestamp" : {
      "origin": "1520627525000",
      "scale": "1d",
      "decay": 0.01
      }
      }
      }
      ],
      "score_mode" : "multiply",
      "boost_mode": "multiply",
      "query": {
      "bool": {
      "must": [
      { "term": { "prospector.type.keyword": "log" } },
      { "term": { "source.keyword": """e:programwdlog.txt""" } },
      { "term": { "host.keyword": "myhost" } }
      ]
      }
      }
      }
      },
      "size": 1
      }


      Then I get a date usually in the beginning of what I indexed, does anyone know how to get better results for when this happens? Or a better way to search for a point in time and get the closest entry.



      Some extra information if needed.










      share|improve this question














      I've been using the following request to get entries close to timestamp, and it works good, until I pick a date that outside of what I have indexed so far. Eg. in the future or in a log that I have stopped indexing some weeks ago.



      # Get log close to date
      GET _search
      {
      "query": {
      "function_score": {
      "functions": [
      {
      "linear": {
      "@timestamp" : {
      "origin": "1520627525000",
      "scale": "1d",
      "decay": 0.01
      }
      }
      }
      ],
      "score_mode" : "multiply",
      "boost_mode": "multiply",
      "query": {
      "bool": {
      "must": [
      { "term": { "prospector.type.keyword": "log" } },
      { "term": { "source.keyword": """e:programwdlog.txt""" } },
      { "term": { "host.keyword": "myhost" } }
      ]
      }
      }
      }
      },
      "size": 1
      }


      Then I get a date usually in the beginning of what I indexed, does anyone know how to get better results for when this happens? Or a better way to search for a point in time and get the closest entry.



      Some extra information if needed.







      elasticsearch






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 12:21









      olahellolahell

      8821924




      8821924
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53481027%2felastic-results-close-to-timestamp-when-no-entries-close%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53481027%2felastic-results-close-to-timestamp-when-no-entries-close%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Calculate evaluation metrics using cross_val_predict sklearn

          Insert data from modal to MySQL (multiple modal on website)